![]() ![]() The auto-number plugin runs pre-create on the creation of a new record. Any new records will be assigned a value by the built-in auto-number plugin. ![]() Adding this property does not affect any data in existing records.V9 Auto-number fields are text fields with an additional property indicating that they are to have auto-numbering applied.This means that you can add auto-numbering to a text field that already exists in your Org – you don't need to deprecate the field and use a new one, or go through the tedious process of removing dependencies, dropping the field, re-adding it with the new data type and putting the dependencies back in. However, experimentation has shown that it is possible to add the feature to an existing text field. Early descriptions of the feature indicated that it was necessary to define a field as auto-number as it was being added to the schema.Today, we're talking about some of the things we've learned about the behavior of auto-numbered fields when importing data or solutions. There are a few installable solutions and external tools available that can do this for you, but that is outside the scope of this blog. It must be done using the API.įor more information, see Microsoft's documentation at. There is a new feature in V9 that allows us to define a field type as "auto-number." As a few Microsoft Dynamics 365 commentators have noted, there is no way as yet to set a field as auto-number from the UI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |