Breaking news from around the world
Get the Bing + MSN extension
End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
Quick query about preallocation of non continuous number sequences.
Microsoft's documentation is clear that unless there is a specific requirement you should use non continuous number sequences in the interests of maximising performance, and so I'm considering switching some number sequences from continuous to non continuous.
However, Microsoft's documentation is not very clear on how preallocation works.
I have been told that it works at user level, and when a user opens for example a new purchase order transaction, AX will generate a pool of purchase order numbers (of the size specified in the "Quantity of numbers" section in the performance FastTab of the number sequences form) in memory which are then available to that user only. Any other user opening a new purchase order transaction would have their own unique, preallocated pool generated which would be available only to them. If the user logs out without using all of their preallocated pool the unused numbers are lost (as is the nature of noncontinuous number sequences so in itself not a problem).
The more I think about it the more odd it seems that the pools are user specific. That could lead to number sequences being spent far more quickly than would be convenient. I would have expected the pool of preallocated numbers to be shared amongst all users. It would reduce the number of calls to the database to create a new pool (performance enhancing in itself) and would leave fewer numbers unused thus increasing the longevity of the number sequence in question. Is that not possible because if the application was being run on multiple AOS it would require shared memory between those AOS to maintain a single pool per noncontinuous number sequence?
I guess my main question is; have I been lied to?
Are preallocated pools really generated and used at user level, or are pools shared by all users and numbers are only lost when transactions that use them are abandoned without being completed?
Thanks in advance.
The preallocation works on the client / user level:
That blog post gives a nice example which will help me illustrate this to users too.
Business Applications communities