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