The sequential segment is generated by SQL and hence uniqueness is guaranteed by SQL.Īll good? Can we go home now? Well, yes, but then you’re going to miss out on the explanation why Elaiza “Mother of Filipinos” Benitez was having an issue with auto number field not generated for records created via portals. Thanks to XrmToolBox Autonum plugin, we can live with that because it’s out of the box, fast and, unlike homegrown brews, has neither deadlocks nor duplicate numbers: There is no user interface to add this type of attribute. The pressure to release was high and some sacrifices were made:Ĭurrently, you can add the attribute programmatically. Finally, the giant woke up and gave us the built-in auto number feature. Over the years we’ve had our share of on-premises hacks, both free and commercial solutions that used variety of techniques: slap-slap-slap™, plugins, workflows, external locking services, to name but a few. So deep was the desire that Dynamics 365 developers went a long way to add this feature. Instead of manually looking up the next available number, calling other users to see if they have any intention of creating a new record in the next few minutes, and placing dibs on that number, users wanted things to be numbered automatically. Auto numbering the new records is one of those. We did mentioned in the past that most of the good inventions are driven by the laziness.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |