Hello -
Via an API, we are trying to update the 7th row under the Details section on the Numbering Sequencing screen but only the first row seems to update even though the NumberingSEQ ID is being referenced. Is there something we are missing?
Thank you,
Ashley
+6@ashleyb NumberingSEQ is only half of that row's key. Each row on Numbering Sequences is keyed by Numbering ID plus NumberingSEQ, and the API needs both on the detail row before it can find it.
PUT /entity/<your endpoint>/<version>/Numbering?$expand=<your detail>
{
"NumberingID": { "value": "APITEST" },
"Sequence": [
{
"NumberingID": { "value": "APITEST" },
"NumberingSeq": { "value": 10137 },
"LastNumber": { "value": "A000200" }
}
]
}
Use your own endpoint's field names. If Numbering ID isn't on your detail entity yet, add it on Web Service Endpoints (SM207060) with Populate.
The other option is the row's id. GET the record with the detail expanded, take the id of the row you want, and send that id in the PUT. Do it in the same session, because these rows have no note ID and the id changes with every login. An id from an earlier login failed for me.
I tested this on 2026 R1 with a custom endpoint and a numbering with 7 rows. Both payloads updated row 7 and nothing else. NumberingSEQ on its own was rejected outright rather than landing on row 1, so if row 1 keeps changing, compare your payload to the one above.
Hi
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
