Using BC 365 SaaS v24.5 in production. Since implementing we have always defined all new Items being created using the ITEM No. Series Code. This past Saturday our users started receiving errors creating new items, that being the record number already exists. Looking in the No. Series table, the Last No. Used had reverted back to an Item No. that was assigned back in August.
First step was looking at the No. Series page to confirm this behavior. Sure enough, the Last No. Used for the ITEM No. Series Code had flipped back to a previous value. We have Change Logs enabled for the No. Series table, and no users had directly modified entries based on accessing the No. Series page. And likewise no configuration packages were applied at all, that could potentially affect either the No. Series table or the No. Series Line table.
Next I pulled up the Item No. and looked at the last modified details. Found the date (likewise matching this past Saturday) and the user. We determined the user at that time was screen shotting the Item card to e-mail another location to request an item transfer.
I'll include screen shots of the No. Series page, along with the screen shot of what the user e-mailed. As you can see the No. field in the Item card has been changed. But I sitll cannot replicate this behavior in a sandbox company. If I change the Item No. and accept the prompt that other records will be modified, and then change the Item No. back to its original value, nowhere do I see the Last No. Used affected.
Any suggestions as to what could've caused this? The user doesn't recall anything specific more than the screen shot. And the Change Logs weren't enabled for the Item table or the No. Series Line table. I need to configure porting out telemetry data to Azure I realize, but will look to do this once we hit 2025.
