Maximo Integration and Scripting

The rowstamp value in REST api responses is returned in byte array instead of integer(BIGINT). Based on my observation this happens only when using SQL Server as DB.
For e.g.
"_rowstamp": "[0 0 0 1 -67 -37 -33 15]",

When you pass rowstamp to Maximo in get request(for e.g. lastfetchts=904687), Maximo expects in int format. So why Maximo needs rowstamp in int format for request but returns byte array format in response.

Could you please advise the reason for this behaviour and is there any settings to change it?

Example: 
http://localhost:9081/maxrest/oslc/os/mxperson?stableId&lean=1&oslc.select=personid&stablepaging=0&lastfetchts=904687&fetchmodedelta=1

Response:


------------------------------
Manoj Sawant
------------------------------



#Maximo
#AssetandFacilitiesManagement
#MaximoIntegrationandScripting

When you enable the fetchmodedelta you get a maxrowstamp header in the response as well. It's the maximum on that page so if you aren't sorting it in a reliably way it's possible that the first page has a higher rowstamp value than the last page. Can you see what you're getting back in that header? I don't have a SQL Server environment available for me to test in but I would assume we would turn that into a friendly value. 

You may have seen this but just be aware there was an issue related to this that impacted Anywhere a few years ago. It wasn't specific to Anywhere so I'd make sure you're on a recent version of the product https://www.ibm.com/support/pages/apar/IJ06814

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

Original Message:
Sent: Sun May 01, 2022 08:58 PM
From: Manoj Sawant
Subject: Rowstamps in REST API response

The rowstamp value in REST api responses is returned in byte array instead of integer(BIGINT). Based on my observation this happens only when using SQL Server as DB.
For e.g.
"_rowstamp": "[0 0 0 1 -67 -37 -33 15]",

When you pass rowstamp to Maximo in get request(for e.g. lastfetchts=904687), Maximo expects in int format. So why Maximo needs rowstamp in int format for request but returns byte array format in response.

Could you please advise the reason for this behaviour and is there any settings to change it?

Example: 
http://localhost:9081/maxrest/oslc/os/mxperson?stableId&lean=1&oslc.select=personid&stablepaging=0&lastfetchts=904687&fetchmodedelta=1

Response:

------------------------------
Manoj Sawant
------------------------------



#Maximo
#AssetandFacilitiesManagement
#MaximoIntegrationandScripting

Hi Steven,

Thanks for the reply. I wasn't looking at headers. The maxrowstamp header returns the rowstamp in int format. This solves my problem.

Below documentation does not cover such topics, please let me know if you have any detailed documentation. 
https://community.ibm.com/community/user/iot/viewdocument/maximos-rest-api-aka-json-api-os?CommunityKey=ed77c224-45e2-47b0-b574-cc31496f9a41&tab=librarydocuments&LibraryFolderKey=6daea7e7-5628-48a6-9791-c272c1e15bae&DefaultView=folder

Appreciate your help. Cheers.

------------------------------
Manoj Sawant
Maximo Consultant
Wipro Technologies
Adelaide
------------------------------

Original Message:
Sent: Mon May 02, 2022 08:55 AM
From: Steven Shull
Subject: Rowstamps in REST API response

When you enable the fetchmodedelta you get a maxrowstamp header in the response as well. It's the maximum on that page so if you aren't sorting it in a reliably way it's possible that the first page has a higher rowstamp value than the last page. Can you see what you're getting back in that header? I don't have a SQL Server environment available for me to test in but I would assume we would turn that into a friendly value. 

You may have seen this but just be aware there was an issue related to this that impacted Anywhere a few years ago. It wasn't specific to Anywhere so I'd make sure you're on a recent version of the product https://www.ibm.com/support/pages/apar/IJ06814

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

Original Message:
Sent: Sun May 01, 2022 08:58 PM
From: Manoj Sawant
Subject: Rowstamps in REST API response

The rowstamp value in REST api responses is returned in byte array instead of integer(BIGINT). Based on my observation this happens only when using SQL Server as DB.
For e.g.
"_rowstamp": "[0 0 0 1 -67 -37 -33 15]",

When you pass rowstamp to Maximo in get request(for e.g. lastfetchts=904687), Maximo expects in int format. So why Maximo needs rowstamp in int format for request but returns byte array format in response.

Could you please advise the reason for this behaviour and is there any settings to change it?

Example: 
http://localhost:9081/maxrest/oslc/os/mxperson?stableId&lean=1&oslc.select=personid&stablepaging=0&lastfetchts=904687&fetchmodedelta=1

Response:

------------------------------
Manoj Sawant
------------------------------



#AssetandFacilitiesManagement
#Maximo
#MaximoIntegrationandScripting

Those are the best resources we currently have available, specifically the Maximo_REST_API_Guide.pdf document. We recently released a Wiki like site for Automation Script (https://ibm-maximo-dev.github.io/maximo-autoscript-documentation/) and we want to do something similar for the REST API. I don't have any sort of ETA on when we can get it done though.

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

Original Message:
Sent: Mon May 02, 2022 09:30 AM
From: Manoj Sawant
Subject: Rowstamps in REST API response

Hi Steven,

Thanks for the reply. I wasn't looking at headers. The maxrowstamp header returns the rowstamp in int format. This solves my problem.

Below documentation does not cover such topics, please let me know if you have any detailed documentation. 
https://community.ibm.com/community/user/iot/viewdocument/maximos-rest-api-aka-json-api-os?CommunityKey=ed77c224-45e2-47b0-b574-cc31496f9a41&tab=librarydocuments&LibraryFolderKey=6daea7e7-5628-48a6-9791-c272c1e15bae&DefaultView=folder

Appreciate your help. Cheers.

------------------------------
Manoj Sawant
Maximo Consultant
Wipro Technologies
Adelaide

Original Message:
Sent: Mon May 02, 2022 08:55 AM
From: Steven Shull
Subject: Rowstamps in REST API response

When you enable the fetchmodedelta you get a maxrowstamp header in the response as well. It's the maximum on that page so if you aren't sorting it in a reliably way it's possible that the first page has a higher rowstamp value than the last page. Can you see what you're getting back in that header? I don't have a SQL Server environment available for me to test in but I would assume we would turn that into a friendly value. 

You may have seen this but just be aware there was an issue related to this that impacted Anywhere a few years ago. It wasn't specific to Anywhere so I'd make sure you're on a recent version of the product https://www.ibm.com/support/pages/apar/IJ06814

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

Original Message:
Sent: Sun May 01, 2022 08:58 PM
From: Manoj Sawant
Subject: Rowstamps in REST API response

The rowstamp value in REST api responses is returned in byte array instead of integer(BIGINT). Based on my observation this happens only when using SQL Server as DB.
For e.g.
"_rowstamp": "[0 0 0 1 -67 -37 -33 15]",

When you pass rowstamp to Maximo in get request(for e.g. lastfetchts=904687), Maximo expects in int format. So why Maximo needs rowstamp in int format for request but returns byte array format in response.

Could you please advise the reason for this behaviour and is there any settings to change it?

Example: 
http://localhost:9081/maxrest/oslc/os/mxperson?stableId&lean=1&oslc.select=personid&stablepaging=0&lastfetchts=904687&fetchmodedelta=1

Response:

------------------------------
Manoj Sawant
------------------------------



#MaximoIntegrationandScripting
#AssetandFacilitiesManagement
#Maximo