An overview of the MISSION: Auto Number form.
To complete these steps, the user performing these actions must have:
- System administrator security role
- MISSION: Auto Number Administrator
To create a MISSION: Auto Number sequence there are three values that must exist on the MISSION: Auto Number record to execute correctly. These attributes are:
Title: The title of the MISSION: Auto Number record, this is automatically created upon save or update of the record. This attribute is used for identification purpose and is read only.
Entity: A selection of system and custom entities in your Dynamics 365 organization. A user selects a value to dictate what entity the completed sequence value will be written to.
Attribute: A selection of system and custom attributes filtered by the selected entity in your Dynamics 365 organization. A user selects a value to dictate what attribute on the chosen entity the completed value will be written to.
Update Null: A flag that instructs the MSSION: Auto Number rule to also trigger on update of a record when no value exists in the target attribute.
Note: When a MISSION: Auto Number rule contains a NULL reference, no value is written to the target record. Set the “Update Null” to true so when the MISSION: Auto Number rule does contain the correct data the full value will be written to the target record.
Date: When utilizing the date and time functions within an MISSION: Auto Number rule, users can specify what date and time attribute to use from the target entity, or alternatively they can select the “Execution Date” which will then use the date and time of when the rule had been calculated. This is particularly useful when importing data into Dynamics 365 where the created-on date and time may differ from the execution date and time of the MISSION: Auto Number rule.
Start Sequence: When using the number functions, a value in the start sequence is required as a user can manipulate the starting sequence number e.g. 1020 instead of 20.
Current Sequence: This value represents the current numbering value that the MISSION: Auto Number rule has consumed when writing a number value to a record. Users may wish to change this value to a different value prior to importing historic data, this way a user can differentiate imported records from ongoing real time transactions.
Status: The status value allows users to specify what “Status” the target record needs to be in prior to a sequence value being generated and applied. This allows you to specify that a value only be generated when either a record is created in a certain status or updated to a certain status when combined with the “Update Null” option.
Sequence: Contains the functions used to calculate the MISSION: Auto Number rule value
Limit Functions (Increases Performance): When this flag is set to true, the functions allowed within the sequence attribute of the record are limited to:
- The date selection is limited to “Execution Date”
Note: Beware of the character limitations of the target attribute prior to creating the sequence. Typically, system attributes used to contain identifying information are limited to twenty characters. Increase the value of the target attribute length prior to using combinations of functions that result in large values being written to the target record.
By design, functions in your MISSION: Auto Number record that reference NULL values will not be written to the target record. Use the “Update Null” flag on the MISSION: Auto Number to write the full value when the referenced attribute contains a value.
An example of this would be:
- You reference the address1_postalcode attribute on the account record in your MISSION: Auto Number rule
- An account record is created but no value is entered in the address1_postalcode attribute
- No MISSION: Auto Number value is written to the target record
- Later, a user corrects the missing data and enters a value in the address1_postalcode
- The MISSION: Auto Number is correctly calculated and the value written to the target record (If the flag “Update NULL” is set to true)