Maximo

Hi!

I found, that when you have an incoming message from MIF (for example application export/import), all fields presented in XML on Maximo level have flag isModified() = True. 

That makes problems in automation scripts or even in OTB functionality if you have validation that filed is modified (mbo.isModifed("xxx") without manual comparison of value with initValue. 

From last, we found, that it has an impact for the integrity of assetancestor table if you have in your income XML for objectstucture field "parent" and the value has not changed. 

To be honest, I am not 100% sure that it was always, because normally  validation mbo.isModified(attribute) was enough, but maybe i had no such usecases. 

So, can anyone confirm it?

If someone is interested, I think it can be just to know. 

If you have in asset import object structure attribute PARENT, that is not restricted (for us it was use case, when we have the same OS for export and import and dont want the user to replace manually parent to newparent tag or column name in CSV), when you import ASSET that is in hierarchy level 3+, even if parent value not changed, then in assetancester table will be deleted relationship of that asset to the top level element (level1), and in assetancester current relationship with asset level 2 will be 1, but not 2, as it should be. 

So, be careful with that