Hello,
I am encountering an issue on the Legal Entities form (OMLegalEntities) where I am unable to change an existing Primary Address toggle or set a newly created address as Primary.
Scenario
In my isolated Development environment, the address grid works as expected. I can create a new address record, and the UI allows me to toggle IsPrimary from No to Yes without any restrictions.
However, in our Pre-Production sandbox environment, which recently received a database refresh from Production, the behaviour is different:
- The Primary column in the address grid is rendered as flat, read-only text with no interactive toggle.
- When creating a new address record, the standard address creation wizard popup — "Do you want to make this address primary?" — does not appear.
Technical Investigation
We have confirmed that security permissions are not the issue. The form is fully in Edit mode, and other fields such as Street, Name, and Purpose remain completely modifiable in both environments.
We traced the framework validation rules down to the form handler layer, which interacts with:
DirParty::isPrimaryAddressChangeAllowed()
Based on our investigation, the method evaluates to false in the Pre-Production environment because it contains historical financial and posted subledger transactions copied from Production.
As a result, the framework dynamically suppresses the UI controls for changing the Primary address in order to protect historical reporting data.
Question
Our team lead prefers an out-of-the-box functional solution.
Is there any standard parameter, configuration switch, or functional setup available through the Dynamics 365 Finance and Operations GUI — for example, within Global Address Book parameters or Organization Administration — that allows us to bypass this validation and change the Primary address directly in a transactional sandbox environment?
If no functional GUI configuration or standard parameter exists to bypass this validation, what is the officially recommended best practice for updating the primary location/address structure of an active operational Legal Entity when the relevant UI fields are hardcoded as read-only?
We would appreciate guidance on the supported and recommended approach, particularly one that avoids directly modifying the underlying database or introducing unsupported customizations.
Thank you for your guidance.
Best regards,
