MIF Data Loading Practices

Flat File Data Load with AUTOKEY fields

MIF framework is XML based, so when loading flat file MIF converts it to hierarchical XML structure. For this conversion, key fields should be provided to properly form the XML. 

 
So, even if we plan to use the auto numbering for any mandatory field (like ASSETNUM), the input flat file must contain some dummy unique asset number for each row to pass the Flat to XML conversion. 
 

Then to restrict the load process from using the dummy value in the file (instead of autokey), the key field ASSETNUM needs to be configured as Set Restricted. 

The Set Restriction can be defined at the object level (within DB configure using the Restrict Attributes select action) or within the object structure (via the object structure application using the Inbound Setting Restrictions select action). This change will impact all integration scenarios.

For XML Data Load, we should not provide the Auto key field (like ASSETNUM) in the input XML file.

Impact of Attribute numbers in Data Loading

       Suppose, if we have State and Region fields in the Maximo Application. When Users select a value in the State field, based on this value, the region data are populated. This works fine from front end.

       If we need to upload the same data through MIF, then there may be a chance MIF will load Region value first, before setting State field. It will led to error or incorrect entry.

       MIF loads the data columns in the order of their "Attribute #" in the Database Configuration. To avoid this scenario to occur, provide a lesser Attribute no. to State field than Region in the Database configuration.