Mutex also is not going to work in multi-server environments


The underlying challenge with a robust auto-number solution is the 'locking' mechanism. Mutex is problematic not only with CRM Online/sandbox, but also if you have multi-server / load-balanced on-premise installations, as Mutex is machine-specific. Two requests could be issued from two different web front-ends simultaneously, each with a valid (as far as each machine is concerned) mutex.
Granted these situations may not be common for most installations, but they do exist.
Closed Jul 30, 2012 at 10:31 AM by jaimieji
changed to lock object and using plugin transaction statement


jaimieji wrote May 2, 2012 at 10:46 AM

Hey there.

Thanks for your message. It definately is a challenge to provide a mechanism in code only for a unique autonumber in multi-server / online / sandbox environment.

If you have suggestions, please let me know as well.


wrote Jul 30, 2012 at 10:31 AM

wrote Feb 14, 2013 at 8:23 PM

wrote May 16, 2013 at 9:55 AM