Swati Madhukar, Author at Microsoft Power Platform Blog http://approjects.co.za/?big=en-us/power-platform/blog Innovate with Business Apps Tue, 07 May 2024 16:00:51 +0000 en-US hourly 1 Announcing General Availability of Block unmanaged customizations http://approjects.co.za/?big=en-us/power-platform/blog/power-apps/announcing-general-availability-of-block-unmanaged-customizations/ Tue, 07 May 2024 16:00:51 +0000 We are excited to announce General Availability of Block unmanaged customizations. This is an environment setting that allows Power Platform system administrators to block direct development in production environment by preventing unmanaged customizations. By blocking any unmanaged customizations and import of unmanaged solutions, admin can ensure that any changes to the environment, specifically the test and production environments, are only going through approved application lifecycle management (ALM) processes that have reliability, safety, and auditing.

The post Announcing General Availability of Block unmanaged customizations appeared first on Microsoft Power Platform Blog.

]]> We are excited to announce General Availability of Block unmanaged customizations. This is an environment setting that allows Power Platform system administrators to block direct development in production environments by preventing unmanaged customizations. By blocking any unmanaged customizations and import of unmanaged solutions, admins can ensure that any changes to the environment, specifically the test and production environments, are only going through approved application lifecycle management (ALM) processes that have reliability, safety, and auditing.

screenshot

This feature will ensure that solution deployments are predictable and consistent and enforces that all changes to production environments go through ALM processes. With this feature, the system administrators will be able to block unmanaged customizations by not allowing direct changes in the environment and by not allowing import of unmanaged solutions in Microsoft Dataverse environments. Unmanaged customizations become the top layer, which blocks managed solutions from being effective. These direct changes in the environment bypass formal ALM processes like testing and approvals.

This feature can be enabled or disabled from the Features area of the environment settings page in the Power Platform admin center. By default, this setting is disabled. The feature cannot be enabled in the default environment. Before enabling the feature, please review the known limitations as some application experiences may be limited.

Once the setting is enabled these restrictions will be imposed for the environment:

  • Import of unmanaged solutions into the environment are blocked.
  • Creation of new solution objects like apps, tables, and forms are blocked.
  • Customizing existing solution objects are blocked.
  • Any attempt to make unmanaged customizations will result in an error returned to the user, such as: “This environment doesn’t allow unmanaged customizations. This was a choice made by your admin, and certain actions won’t be available or will be view only.”

The following operations are not blocked by this feature:

  • Change of environment variable values.
  • Enabling or disabling of solution objects. For example, turning Power Automate flows on or off.
  • Assigning of ownership or sharing of table records.
  • Solutions operations like remove active customizations.
  • Creation and export of unmanaged solutions.

Learn more

The post Announcing General Availability of Block unmanaged customizations appeared first on Microsoft Power Platform Blog.

]]> Working with solution dependencies for objects made easier http://approjects.co.za/?big=en-us/power-platform/blog/power-apps/working-with-solution-dependencies-for-components-made-easier/ Tue, 26 Mar 2024 16:00:23 +0000 We are super excited to announce the refreshed look of solution dependencies for component. The solution dependencies page for component is better organized, easy to understand and loaded with essential actions that helps to identify the dependencies and take appropriate actions.

The post Working with solution dependencies for objects made easier appeared first on Microsoft Power Platform Blog.

]]> We are excited to announce the refreshed look of solution dependencies for solution objects. The dependencies page is now better organized, easy to understand and loaded with essential actions that helps to identify the dependencies and take appropriate actions.

 

The purpose of the dependencies page is to show inter dependencies between solution objects when an object is dependent on another object. The system tracks dependencies so that it can block the deletion of an object to avoid breaking dependent applications and features. With the new dependencies page improvements, it will help to understand, inspect and take action with the objects involved in these dependencies.

 

We have added tabs that focus on dependencies that will block deletion (Delete blocked by), viewing other components that use this component (Used by) and viewing other components that this component uses (Uses). We have also grouped dependencies by solution to make it easier to understand the solutions that are involved in these dependencies.

 

We have included multiple actions that can be taken for each dependency. The actions can be used to:
  • Open and inspect the object.
  • Delete the object.
  • Remove dependency between the objects.
  • Open documentation to learn more about the dependencies for that object type.
  • Delete the solution taking dependency on the solution object.

 

The post Working with solution dependencies for objects made easier appeared first on Microsoft Power Platform Blog.

]]>