We would like to propose an enhancement to Microsoft Dataverse regarding the customization capabilities of standard currency fields, specifically the ISO Currency Code (isocurrencycode) column within the standard TransactionCurrency table.

During a recent Dynamics 365 Field Service and Business Central integration scenario, our organization encountered a synchronization issue related to currency configuration between systems. As part of our troubleshooting efforts, we attempted to increase the character length of the ISO Currency Code field in Dataverse to accommodate integration requirements.

While the modern Dataverse table designer allows editing of certain field properties such as MaxLength, changes made to the isocurrencycode attribute are not persisted by the platform and revert after refresh. Upon further investigation with Microsoft Support and referencing official documentation, we understand that this behavior is expected because:

• The Currency (TransactionCurrency) table is a standard Dataverse table
• The isocurrencycode column is a standard (default) column
• Microsoft documentation states that system and standard columns cannot be modified

Although this restriction is understandable from a platform integrity standpoint, it introduces challenges in real‑world integration scenarios where external enterprise systems (such as ERP platforms like Business Central or third‑party financial systems) may have differing requirements for currency code formats or extended identifiers.

Business Impact

Currently, there is:

• No supported method to extend or override the ISO Currency Code metadata
• No configurable integration‑level mapping for this field
• No platform‑supported workaround for customers integrating with systems that require longer or alternate currency identifiers

As a result, organizations must:

• Implement unsupported workarounds
• Create parallel custom fields and mapping logic
• Or redesign integration mappings outside of Dataverse

This increases:

• Integration complexity
• Maintenance overhead
• Risk of data inconsistency across connected systems

Suggested Enhancement

We propose that Microsoft consider introducing one or more of the following capabilities:

• Allow controlled metadata extension of standard currency attributes such as isocurrencycode
• Provide integration‑layer mapping or aliasing for currency codes between Dataverse and external systems
• Introduce a configurable override field or alternate identifier for currency synchronization scenarios
• Enable customization of selected standard column properties (e.g. MaxLength) where it does not impact financial calculations or exchange rate logic

This would allow organizations to maintain compatibility with enterprise integrations while preserving the integrity of the Dataverse currency model.

Expected Outcome

Providing flexibility in handling currency identifiers at the integration layer would:

• Improve interoperability with ERP systems
• Reduce unsupported customization attempts
• Minimize reliance on custom mapping logic
• Enhance adoption of Dataverse in enterprise integration scenarios

Additional Context

This request is based on a Dynamics 365 Business Central and Field Service synchronization scenario where modifying the ISO Currency Code field length was investigated as part of troubleshooting integration failures.