Thank you Steve and Sankar, you are correct. It needs lean parameter or prefixes on attribute name.
Original Message:
Sent: 07-16-2025 08:51
From: Sankar Ganesh V S
Subject: MAS Manage v9.0 - JSON Mapping inbound errors
Hi Aakash,
As suggested by Steven, you can either,
Use 'lean=1' as parameter
Or
Prefix 'spi:' in all payload fields
Thanks!
------------------------------
Sankar Ganesh V S
DXC Technology
Original Message:
Sent: 07-15-2025 12:41
From: Aakash Saxena
Subject: MAS Manage v9.0 - JSON Mapping inbound errors
Hi All, I am trying to leverage JSON mapping application for Maximo inbound integration. The purpose to use JSON mapping is to do transformation as the incoming fields don't match with Maximo object and I want to keep transformation logic light weight and on maximo side. I have duplicated OS for MXASSET and configured Json mapping using below data and mapped the source and target in Properties tab.
{
"name": "TAG001",
"short_description": "Air Handler Unit",
"model_name": "Model-123",
"serial_number": "SN-456789",
"asset_location": "Room 204",
"install_date": "2025-07-01 12:00:00",
"siteid": "TEXAS",
"orgid": "EAGLENA"
}
When I hit the POST Message with URL - https://hostname/maximo/api/os/osname , I am getting Site Id not found error. The Site ID is active and part of the organization in Manage.
{"oslc:Error":{"oslc:statusCode":"400","errorattrname":"siteid","spi:reasonCode":"BMXAA4153E","errorobjpath":"asset","correlationid":null,"oslc:message":"BMXAA4153E - null is not a valid site. Enter a valid Site value as defined in the Organization Application."
The same error appears even if I replace the JSON data with actual Maximo attributes.
Any pointers on why this is occurring?
Thanks
#Integrations
------------------------------
SA
Accenture
------------------------------