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
.
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
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.
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
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/
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,409
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
