Nota
L'accesso a questa pagina richiede l'autorizzazione. È possibile provare ad accedere o modificare le directory.
L'accesso a questa pagina richiede l'autorizzazione. È possibile provare a modificare le directory.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
Extended data types (EDTs) have a rich extension model that lets extenders change specific behaviors.
To provide an extensible solution, keep the following guidelines in mind when you work with EDTs.
Label and help text
An extension can change the label and help text properties, but only one value can remain. If multiple solutions change the label of the same EDT, the various labels are, in functional terms, mutually exclusive. Therefore, you can't install those labels on the same system.
String size
You can define the string size only on root EDTs. The system uses the largest value that is defined across the EDT and its extensions.
For derived EDTs, an extension can't change the string size, because that change breaks the IS-A relationship between the EDTs.
Assignments to string EDTs truncate the string to match the defined string size.
Extends
An extension can't change the extends property. Any change that you make to this property after release causes a breaking change. Therefore, make sure that the property is set correctly before release.
If you set this property, neither you nor extenders can make changes to the string size later.
Avoid unnecessary dependencies. For example, don't extend generic EDTs such as Name and Description.
Number of decimals
You can't change the Number of decimals property by using an extension.
If you set this property to True, extenders can change the number of decimal places.
If you set this property to True, make sure that the following conditions are met:
- All truncation logic honors the number of decimal places that you specify on the EDT, so no implicit or hardcoded rounding occurs.
- You don't assign the value to other incompatible EDTs that don't correctly handle rounding.