Block Unmanaged Customizations
#Solution, #UmanagedSolution, #BlockCustomization, #PowerPlatform, #Dataverse
Last updated
#Solution, #UmanagedSolution, #BlockCustomization, #PowerPlatform, #Dataverse
Last updated
Hello, my friends,
Recently, Microsoft has introduced a new feature allowing Power Platform system administrators to block unmanaged customizations in Dataverse environments. This feature is currently in public preview and can be enabled as an environment setting in the Power Platform Admin Center.
In the Production environment, managed solution components are not directly customizable, but you can add an unmanaged layer to them through the Default Solution. This way, you can modify the managed components as you wish. An unmanaged layer is created when you make changes and customizations within the application without any limitations. And with the unmanaged layer lets you alter components such as tables, fields, forms, views, business rules, workflows, ... without locking them. However, in some cases, you must prevent any unmanaged customizations in the Production environment to avoid unexpected issues or bugs.
That's a great update from Microsoft. In last my project, I remember that the client's BA Team was involved in developing the solution within our team. My Team and me so very very tired and hard to track and find why those managed components have been updated and who made this change. 😂 😢
This feature lets me link to the Managed Properties is "Can be customized" property which is configured for each entity. If you set this property for an entity, you cannot modify the entity in another environment when you import a managed solution (and of course, this entity must be part of this managed solution ☺️)
This property will take effect only after the component is exported and imported as part of a managed solution.
Okay... after enabled, I will export my solution as a managed solution and import it to the PROD environment.
Now, check with me. In my PROD environment: I haven't enabled the Block unmanaged customizations (Preview) feature yet and my managed solution "BlockEntity" - is used to block any customize for the entity Visit.
Results: Just only the entity "Visit" cannot be customized, and you can customize the remaining entities (for instance: the "Account" entity). 🎉
This feature allows you to disable customization for individual entities. You can also choose which customization actions to block.
For more details, you can find here.
Configure: Environment > select specific environment > Setting > Feature. -- Opening the Default Solution and checking now...
Once you enable this feature for the environment, you will lose the ability to customize any entities in the Default Solution.
Thank you and hoping well. ☺️⭐ [NTD]yns.asia ...invite me a cup. ☕ Thank you. ❤️
