Modify extended data types (EDTs) through extension
Dynamics 365 for Finance and Operations is now being licensed as Dynamics 365 Finance and Dynamics 365 Supply Chain Management. For more information about these licensing changes, see Dynamics 365 Licensing Update.
There are several properties that can be customized on existing extended data types (EDTs) through extension:
- Help text
- Form help
- Country region codes
- String size
- You can only modify the value if the EDT does not extend from another EDT.
- You can only set the new String size to a value equal to or larger than the base EDT value.
- Decimals (NoOfDecimals property)
- For more information, see Extending decimal point precision for selected data types.
You modify the properties as you would for newly added elements, using the property sheet.
After compiling the code, you can see the changes in the application.
You can view the created extensions in the Application Explorer in Visual Studio.
If the EDT is modified in more than one model
If multiple ISVs have extended the same extended data type, the properties of the EDT from the model with the highest Model ID (closest to USR) will be used. If there are multiple models with changes in the same layer, changes from the model with the highest Model ID will be used. For example, if ISV 1 modified the label of ItemId to “Awesome item number” in model AwesomeModel (USR layer) with ID 15, while ISV 2 modified the label of ItemId to “Super item number” in model SuperModel (USR layer) with ID 12, the end user would see “Awesome item number” in the user interface instead of “Item number”.
Instead of extending an existing EDT, you can create a new one, deriving it from the existing EDT. This allows you to edit more properties than you could edit using the extension approach. This means that you would need to modify the fields using this EDT to use your new EDT.