Unmanaged Layers in Managed Solutions With Power Platform managed solutions, it’s easy to assume that all customisations remain neatly packaged and tightly controlled. This is not always the case! Most components in managed solutions can be edited. This is true […]

Solution Dependencies When importing a managed solution into a new Power Platform environment, you might experience obscure solution dependency errors that prevent the import completing successfully. The errors, typically reference component called GUIDs, and often without much further information. This

Introduction When it comes to deploying Power Platform solutions automatically, you have two main options: Power Platform Pipelines and Azure DevOps Pipelines. Each has its strengths, and knowing the right one to use can help your deployment strategy.  In this

Solution Management Pipelines and Git are valuable tools, but for small applications, they might not always be necessary. If you’re developing using an unmanaged solution in a Dev environment and deploying a managed solution to Prod, it’s essential to have

Upgrades and Updates When importing a managed solution, a decision is required to either upgrade or update the existing solution. Upgrades are intended for deploying significant changes, like new features, structural changes, or adding new tables. The ‘Stage for Upgrade’

Power Platform solutions are version numbered using the format: <Major>.<Minor>.<Build>.<Revision> For example, when a solution is created in a development environment, it will initially have the version 1.0.0.0. Revision Number The first time the solution is exported, the Revision is

What Is Administration Mode? Administration mode is an environment config setting that allows admins to restrict access to a particular environment preventing users from creating, changing or deleting any data. This is enforced because administration mode blocks access to Dataverse for

Recently I was investigating removing a component in a production environment, that stubbornly remained. It had me thinking for longer than it should, but after first diving down a couple of rabbit holes, I realised what the issue was. The

One of the powerful features available when creating a new Power Platform environment, is the ability to create custom environments tailored to specific business needs. An often overlooked but valuable customisation is assigning an environment custom URL. Why Assign an

Flow Ownership In my recent articles, Notes on Flow Ownership and Flow Execution Ownership I discussed in whose name the different types of flow are run. Instant flows run in the name of the user who triggers them as “Run-only”

It can take a while for newly created or newly shared environments to show up for users. The Microsoft guidance says it may take up to 10 minutes for them to become available in the Power Platform developer studios and

Sharing model-driven apps is slightly different to sharing canvas apps. In this post I’m going to briefly cover what you need to be aware of, together with some supplementary info that will help make the process clearer. How is Sharing
Scroll to Top
Scroll to Top