MIF- Object Structures: Alias Conflict

January 12, 2010 in Maximo, Maximo 7, Maximo: MIF by Michael Chrisman 1 Comment

We need to take a closer look at the Alias Conflict. An Alias Conflict is when you have column name that are the same in different MBOs. For example, if you create a MOS (MIF Object Structure) that includes ASSET and ASSETSPEC, then you will have a conflict of fields like ChangeDate and ClassStructureID and as both MBOs have these fields. Of course, this is not an issue if you are using XML message format. This only is an issue if you select the “Support flat structure.” If you have selected the “Support Flat Structure” and click Save, Maximo will then run a Conflict Analysis. If there are conflicts, Maximo will check the “Alias Conflict” check box.

This check box is important because if it is checked, Maximo will not let you add it to an External System. Resolving conflicts is pretty easy as when you select the Add/Modify Alias screen, it will put all the fields that are in conflict first.

You can then just give new aliases to the columns in conflict and save.

However, there seems to be a bug in the logic of the Conflict analysis. If, instead of giving the conflict fields new aliases, you excluded them (using the Exclude/Include fields screen), the conflict analysis would still show a conflict. And if you went the Add/Modify Alias screen, you would not find any fields listed in conflict. I don’t know the conflict analysis does not excluded fields that you have marked as “Excluded” or if there is some underling logic that still needs the columns to have different names. The solution is to, before you exclude any fields, go to the Add/Modify Alias screen and clear up any conflicts. Then you can exclude the fields and it will all be good.