Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Back to discussions
Expand all | Collapse all

inbound integration - create parent object and use that object in child object in same message

  • 1.  inbound integration - create parent object and use that object in child object in same message

    Posted Thu July 14, 2022 04:55 AM
    Hi,
    Is it possible to have a single inbound integration message that creates a record, and then uses that record
    i.e. we have an object of:
    ASSET
       ASSETLOCRELATION (part of Maximo Linear)

    I want to create an ASSET with ASSET.ASSETNUM = 1000, and then in the same message create a record in ASSETLOCRELATION table with ASSETLOCRELATION.SOURCEASSET = 1000

    Currently it throws BMX error of 'asset does not exist'.

    This is using Maximo Spatial integration (enterprise service > end point > JSON mapping)
    Is this possible through some fancy Object structure configuration, or only with an automation script?

    ------------------------------
    Zoltan Kelly
    Vic/Tas User Group Leader
    Asset Information Improvement Specialist, Melbourne Water
    zoltan.kelly@melbournewater.com.au
    +613 9679 7732
    ------------------------------

    #Maximo
    #AssetandFacilitiesManagement


  • 2.  RE: inbound integration - create parent object and use that object in child object in same message

    Posted Thu July 14, 2022 08:39 AM
    I haven't tried this exact import but took a glance at how we enabled this from the UI and it looks like when a new ASSETLOCRELATION record is added we populate the values from the owner if the owner is an ASSET and suppress validation on that field. Normally, this autogenerated data is deleted but it seems like in your scenario you want that for this object. Open your object structure in the Object Structure application and open the Advanced Configuration dialog. Uncheck the "Delete Auto-generated Data" on the ASSETLOCRELATION object. That should allow the initial defaulting of the values to come in from the ASSET which suppresses validation. If you provide the values and they're different than our defaults those should get copied to the record still. 

    Let me know if that works for you. If not I can try and play with it a bit. 



    ------------------------------
    Steven Shull
    ------------------------------

    Original Message


  • 3.  RE: inbound integration - create parent object and use that object in child object in same message

    Posted Fri July 15, 2022 11:59 AM
    My view on this is that when you go to modify the Object Structure is to first duplicate it then do the modifications.  This will help you ensure you have an original to go back to for change management.  Hope this helps.

    ------------------------------
    Bradley K. Downing , MBA
    Solutions Engineer
    IBM
    Bakersfield CA
    ------------------------------

    Original Message


Related Content