In the last few months I have been working on upgrading the customer´s unmanaged environments to managed. The customer had been working with unmanaged environments for about 5 years, and after joining, this has been one of the first things that I determined would be needed for this customer.
A couple of months ago, I wrote a post about changes on the creation of Application Users and the ability to manage this via the Power Platform Admin Center. Not much time has passed, and a few additions have been added to the Admin Center, which allows to manage Users, Teams and Security Roles. We are still missing some functionality to reach parity with the classic interface, but we are on our way.
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.
Yesterday, June 8th, Microsoft announced the public preview availability of the new Model-Driven App Designer (or Modern App Designer). You can read about the announcement on the Microsoft Power Apps blog in the link below
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.
As we all know when we display our grids in flow (responsive) mode, the style of the grid changes from table style into card view style. When this happens, what we see is a bubble that shows up next to each card item, and we don’t really have much control over the colors or the text within those bubbles.
It seems like this was only a few days ago, but based on the sample that was published by Microsoft it’s been almost 2 weeks since Microsoft released CRUD support on Virtual tables.
In a recent implementation I was working on a Canvas app that was supposed to display records to the users in a Nested Gallery. The users that would be accessing the gallery would always have permission to see the parent gallery, but not everyone had permissions to view the child gallery.
With everything that is going on around ALM and CI/CD and how to implement an automated deployment process with Azure Dev Ops of Github actions, there are still many organizations that have a lot of work that needs to be done before they can turn the switch over.
In one of our recent requirements, we had to log changes to certain fields in a few different entities. Since we needed the value of the field before and after the change, the logical option was to use plugins and adding a pre-image step to it in order to save that data.
