Numbering Sequences API Only Updating First Row

@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 ​@Steve Milner - We can’t seem to get it to work... One thing I forgot to mention is we currently have it set to Auto # however our purpose of doing this is to Manual # one of the rows instead. Do you think this could be interfering?

@ashleyb No, Auto numbering isn't what's blocking it. My APITEST numbering had Manual Numbering cleared, same as yours, and the row 7 update went through.

Manual Numbering isn't a row setting, though. It's the check box in the Summary area of Numbering Sequences, it belongs to the numbering ID, and it covers every row under that ID. A detail row only holds Branch, Start Number, End Number, Start Date, Last Number, Warning Number and Numbering Step, so there's nothing on row 7 that makes only that row manual, through the API or on the screen. Checking Manual Numbering turns it on for every document that uses that numbering ID, and each of those then needs its number entered by hand.

If you still need the row update itself, post the request body and the response you get back. A failed PUT returns an error message, and that will show where it's getting stuck.