You create functionality for a company. The functionality includes a Microsoft Dataverse table with a form for data entry. The functionality will be distributed to other lines of business in the company, each with its own Dataverse environment.
New forms must not be created in order for updates to the functionality to work correctly.
You need to package the new functionality for distribution.
What should you do?
A managed solution is the correct distribution package for downstream Dataverse environments because its components are controlled by the publisher and form part of a governed ALM process. Disabling the table's ability to create new forms prevents recipients from adding replacement forms that would undermine the assumption that future updates target the distributed form. Option A includes only the needed form but does not enforce the requirement that new forms must not be created. An unmanaged solution is intended for development and would allow direct changes in each target environment, increasing divergence and making upgrades unreliable. A patch is a versioning mechanism for a parent solution, not a security switch that independently prevents form creation. The publisher should develop in an unmanaged solution, set the managed properties on the table or component, export the solution as managed, and import it into the target environments. Microsoft documents managed properties as controlling which customizations are permitted after a managed solution is installed.
Study Guide alignment: Create a foundation for intelligent applications.
Currently there are no comments in this discussion, be the first to comment!