MxLoader

Hi everyone.

I'm encountering another problem uploading things with MXLoader.

This time is with Assets using the MXASSET application.

I think it's good for us to create something like the following asset structure:

ASSETNUM       LOCATION                           PARENT

TVM.01              PLATFORM.TVM1

CNA.001            PLATFORM.TVM1.CNA     TVM.01

But with MXLoader the asset CNA.001 go in the location PLATFORM.TVM1 without displaying errors. Instead it should go to PLATFORM.TVM1.CNA location.

I can assign the correct location (and parent) creating it manually on Maximo web interface.

There's a way to upload assets as I want? (with asset location not in the same location of the parent)

PS: Yes, uploading assets, I have also the columns SITEID, DESCRIPTION and STATUS populated.

Thanks for who will replay

This is not really specific to MXLoader. The object structures for asset have an inbound processing class MaxAssetProcess. This is used for taking restricted values like location, parent, etc. and setting it on the newly created asset or executing the move properly on an existing asset. The problem is the setAdditionalData method sets the location field first before setting the parent and the parent attribute has a class associated to it that sets the location to the parent asset's location. I can't say whether this is working as designed or not... but I would open a support case with IBM because I think we should be keeping the location if it's provided instead of overriding it from the parent asset. 

In the interim, what you could do is utilize an inbound object structure automation script to set the location field again. We document this type of automation script here in our wiki: https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/integration/osevents

The Simple solution could be add that asset twice:

The first time it get created (with the wrong location) and the second time, because it is already created, it will just update the location.