As Microsoft is still making changes to connection references, I have been trying to get it to work with a service principal account, and account a few interesting points that are important for anyone who will be developing and deploying Power Automate flows using the Service Principal Connection reference.
In this article, I review the required steps of building and deploying your Power Apps solution from your Development environment to your test and production environments. We will add a approval trigger from Test to Prod, Unpack the solution and publish your managed solution as an artifact so that it can be used to import to the higher environments.
There are various organizations that for whatever reason, whether it be trust or security are not comfortable using the Microsoft-hosted agents, and would like to use self-hosted agents within their own corporate environment.
In this article, I will go through the steps of creating a self-hosted agent, and then configuring a pipeline that will move your solution between the different environments.
A few weeks ago, I wrote a blog post about embedding a Canvas App in a Model Driven form, and compared the options of whether, in my case I should have embedded the app using the Canvas App control, or as we implemented using an iframe on the form.
For those of us who have been using Microsoft Dynamics from the early days, the only names that we ever knew for the data schema elements has been entities, fields and attributes, records, and for the different fields types where we will be seeing the changes applied option sets, picklists and two option values.
