Assumedly auto-generated numbers that have sequential numbering are employing a database sequence. Generally the database engine limits the number of those available. How many auto-generated fields with sequences can an org have?
TIA
Apparently there are plenty on the server but, in the cloud there is the question of sharing --
https://jonshaulis.com/index.php/2018/06/27/how-many-sequences-can-i-have-in-sql-server/
I haven't seen anything discussing limits on number of the autonumber fields you can have in your organisation, but I would start with what is it that you need to do that requires a lot of them?
Note, there is a limit on the number of custom entities that you can create in CRM and this would impart a practical limit
Good question. Following the pattern used by msdyn_salesordernumber, I want to use them as identifiers for the Dual Write integration keys on custom entities. Shouldn't be more than a couple of handfuls per org.
So basically you need 1 auto number field per Entity - which is probably not going to be an issue.
It is managed by SQL Server as per the brief mention in docs.microsoft.com/.../create-auto-number-attributes
.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Tom_Gioielli 179 Super User 2025 Season 2
#ManoVerse 110
Gerardo RenterÃa Ga... 61 Most Valuable Professional
