Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Lewis Rosenberg]

Up

0

Down

::

If auto-numbering, that certainly should not happen. I assume you are manually assigning numbers from that series. What document is the number series for?

[Ian Ray]

Up

0

Down

::

Please explain more.

No. Series does not check for duplicates. You can look at the flow of No. Series and No. Series – Impl. codeunits to see.

The only place a duplicate would be rejected is if this is the “No.” field in a table where No. is the primary key or part of a unique key and the key already exists in the same table.

[Hardik Gupta]

Up

0

Down

::

Hi @cfarmeresprigas-com

I’ve run into this a few times over the years, and it’s usually not the No. series itself, but something around timing, integrations, or custom logic touching the number assignment. If you’re able to share a bit more context around where it’s happening (document type, posting vs creation, any integrations/customizations), it’ll be easier to narrow down.

Happy to take a quick look or jump on a short call if that helps.

[Vishal Pandey]

Up

0

Down

::

Hello Chris,

Yes, this can happen, but not in a clean standard Business Central setup. Normally, BC does not generate duplicate numbers if the No. Series is configured correctly and duplicates are not allowed. When duplicates appear, it’s usually due to custom AL code assigning numbers manually, integrations or imports bypassing the standard numbering logic, concurrent users creating records at the same time, or failed/unfinished transactions. In most cases, the issue is related to customization or concurrency rather than standard system behavior.