Microsoft Dynamics 365 9.0 new features - Auto Number
Article on What’s new in Microsoft Dynamics 365 v9 auto-number New Feature. Below is the video explaining every thin about Dynamics 365 v9 auto-number.
Microsoft Dynamics 365 9.0 new features by Dynamix Academy
SITUATION TILL NOW
- OOTB Auto Number Feature was supported for limited Entities listed below
- Contracts
- Cases
- Quotes
- Orders
- Invoices
- Campaigns
- Articles
- Categories
- Knowledge Articles
- Implement Auto Number Logic on your own Use Custom Solutions in Marketplace for Auto Numbers
Dynamics 365 v9 auto-number
- With the Dynamics 365 for Customer Engagement apps version 9.0 release, you can add an auto-number attribute for any entity.
- Currently, you can add the attribute programmatically. There is no user interface to add this type of attribute.
- UI will be coming soon .
- You can also convert existing fields to Auto Number fields programmatically.
- You can create an auto-number attribute in the same way you create a string attribute using the StringAttributeMetadata class except that you use the new AutoNumberFormat property.
- AutoNumberFormat property to define a pattern that includes sequential numbers and random strings by composing placeholders, which indicates the length and type of values that are generated.
- The sequential segment is generated by SQL and hence uniqueness is guaranteed by SQL.
- You cannot create an auto-number attribute that uses any other special kind of format such as Email, Phone, TextArea, URL or any other existing formats.
Dynamics 365 v9 auto-number New Feature
*
Dynamics 365 v9 auto-number *
Auto Number Format Supports the following format tokens:
- Static String
- DATE:[format] e.g. ddmmyyyy
- SEQNUM:size
- RANDSTRING:6
AutoNumberFormat options
These examples show how you can configure the AutoNumberFormat property to get different results:
| AutoNumberFormat value | Example value |
|---|---|
CAR-{SEQNUM:3}-{RANDSTRING:6} |
CAR-123-AB7LSF |
CNR-{RANDSTRING:4}-{SEQNUM:4} |
CNR-WXYZ-1000 |
{SEQNUM:6}-#-{RANDSTRING:3} |
123456-#-R3V |
KA-{SEQNUM:4} |
KA-0001 |
{SEQNUM:10} |
1234567890 |
QUO-{SEQNUM:3}#{RANDSTRING:3}#{RANDSTRING:5} |
QUO-123#ABC#PQ2ST |
QUO-{SEQNUM:7}{RANDSTRING:5} |
QUO-0001000P9G3R |
CAS-{SEQNUM:6}-{RANDSTRING:6}-{DATETIMEUTC:yyyyMMddhhmmss} |
CAS-002000-S1P0H0-20170913091544 |
CAS-{SEQNUM:6}-{DATETIMEUTC:yyyyMMddhh}-{RANDSTRING:6} |
CAS-002002-2017091309-HTZOUR |
CAS-{SEQNUM:6}-{DATETIMEUTC:yyyyMM}-{RANDSTRING:6}-{DATETIMEUTC:hhmmss} |
CAS-002000-201709-Z8M2Z6-110901 |
Things to keep in mind
- At time of creating new Auto Number attribute, make sure Max Length of field should be greater than total length of Auto Number Format string.
- After creating Auto Number Attribute programmatically, you need to add that field on Form, Views , Quick Create Forms etc. manually .
- New Auto Number Field with be locked for edit, hence not possible to modify its values later.
- You can modify, the auto number format after its is created again programmaticaly.
Also read previous posts of Dynamix Academy about Microsoft Dynamics 365 below:
Also Find Useful references below:
Follow Dynamix Academy on different Social Media platform :
Facebook: https://goo.gl/UQH3Eg
Twitter: https://goo.gl/d84Qw9
YouTube: https://goo.gl/wwznrB
