Applies to Product - Microsoft Dataverse
What’s happening?
Customers have reported issues where form changes made in a development environment do not reflect after deploying the managed solution to a different environment. Specifically, there are instances of duplicate fields appearing in forms, and changes to field positions not being retained post-deployment.
Reason:
The underlying cause of this is related to the management of forms across multiple managed layers. When a form is managed by multiple solutions, changes made in one layer may not be tracked correctly, leading to discrepancies in the expected behavior of the form after deployment.
Resolution:
- Verify that the form in the development environment is in an unmanaged state before making changes.
- Ensure that any changes made to the form are properly tracked in the XML file associated with the solution.
- If a field is duplicated, hide one of the fields to prevent the creation of active layers that could complicate the form's behavior.
- Review the customization.xml file to check if the impacted components have the correct solution action attributes.
- Follow best practices for managing forms, including maintaining as few layers as possible to avoid unpredictable behavior. For more information, refer to the documentation on customizing managed forms.
- If issues persist, consider creating a new form to manage the changes more effectively, as this may simplify the management of the solution layers.