Hi Prashant ,
thank you for the summary which confirms what I knew.
That's exactly why I was looking for a single REST API call that would work like the MIF Sync-AddChange.
Thanks to a suggestion from @Biplab Choudhury I tried the BULK method and from initial tests it seems to address my requirement well.
------------------------------
Diego Visentin
Tempestive S.p.A.
------------------------------
Original Message:
Sent: 02-22-2024 11:13
From: Prashant Sharma
Subject: NextGen REST API vs AddChange
Hi Diego
- Create the record if it does not exist: POST call with Params
- Update the primary record if it exists: POST call with Params for a record ID and x-method-override : PATCH
- Update sub-records if they exist & leave sub-records not included in the request intact : POST call with Params for a record ID and x-method-override : PATCH and patchtype:MERGE
Framework matches child and update if finds match, otherwise leave them as it is or add new child if not found associated with Parent.
Hope this clarifies.
------------------------------
Prashant Sharma
Sedin Technologies
Connect with me @ https://www.linkedin.com/in/psharmamaximo/
Learn Maximo with me @https://www.youtube.com/@reliabilityodyssey/
#IBM Champion 2022
#IBM Champion 2023
#IBM Champion 2024
Original Message:
Sent: 02-20-2024 13:10
From: Diego Visentin
Subject: NextGen REST API vs AddChange
Hi,
with the NextGen REST API, do you have any idea what combination of request method and the 'x-method-override' and 'patchtype' headers is required to achieve behaviour identical to the Synch&AddChange of the MIF (link)?
That is:
- create the record if it does not exist
- update the primary record if it exists
- update sub-records if they exist
- leave sub-records not included in the request intact
#Integrations
------------------------------
Diego Visentin
Tempestive S.p.A.
------------------------------