Have you ever written a Azure DevOps pipeline for the Power Platform and everything works as expected until you reach the Command Line Script to push your changes to your Azure DevOps Repo?
A few weeks ago Microsoft announced the availability of SQL Server Environment variables which will be able to support your Power Apps deployments as part of an ALM Process
While working on a recent project to replace a low code platform with the Power Platform, one of the requirements that we had was to replace some of the Excel export and import functionalities that the existing system had to be able to send large Excel files into various other systems to be analyzed and consumed.
If you are keeping track of changes in some of the connector actions, you might have noticed recently that Microsoft marked the Send an HTTP request action as deprecated and mentioned to use the Send an HTTP request V2 action instead.
The AAD Users virtual table that was added to Dataverse has been a lifesaver for a lot of applications, especially when using Power Apps licensing as they provide the full subset of Active Directory users. When using Power Apps licensing, not all users are automatically synched to the Users table, so that is a great addition.
Up until recently the email description field or the body of the email have been stored within the Microsoft Dataverse data store. This is going to be changing in the coming months where the email description field will be moved to an Azure Blob Storage
Have you worked on a project with multiple teams where you need to update the changes from all instances into a single integration instance? There are multiple options for doing this, some manually and some automated, but in this post I will discuss a little hack (using Azure DevOps for deployment) that can be used to deploy the separate solutions into a single solution in the target instance.
Late November last year, Microsoft released an experimental feature in Canvas apps to allow co-authoring, so that multiple users can work on the app at the same time. Currently, prior to this feature, if a user is working in Canvas Studio, any other user that will try to login to Canvas Studio will be blocked stating that it is locked by the previous user.
I have been working with a client for the past year or so, where they have been using the Data Export Service to write data from their Dataverse environment to an Azure hosted SQL Server.
In late 2019, I wrote a blog article on how to configure oAuth authentication for Dataverse by creating an App Registration record in Azure, and the configuring the App Registration/User account in your Dataverse environment so that it can be consumed as an Application User or Service Principal.
