As always, I try to bring some real world scenarios that I was required to implement and modify the logic a little bit. In today’s app we will be creating a project record and adding and removing membership to the project while adding custom logic to adhere to special circumstances. You can do this of course with a model-driven app, but the main requirement was to make sure that the percentages of ownership on the Project is always 100%.
A few days, on January 27th, Microsoft release the documentation for the 2021 release wave 1 plan. As there are hundreds of doc pages containing the features that will be released between April and September 2021. You will be able to get access to some of these features starting the beginning of February (in preview mode), and then it will be rolled out to the different regions in April.
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.
To start the year, I would like to review Adaptive Cards, where last summer I had a Power Storm session with a couple of my fellow MVPs, Alex Shlega and Linn Zaw Win to get a little more familiarized with using Adaptive Cards, adding them to Cloud flows and Microsoft Teams, and sending adaptive cards via Outlook. About 5 months passed since then, and now I had the need to build something for a project that I am working on.
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.
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.
As part of the controls that are available for Model Driven apps in unified interface we have the Option Set PCF custom control. Recently I encountered a weird behavior in these controls. I am not sure whether Microsoft would consider this as a bug or a feature, but I wanted to discuss this here, so that possibly it can help other who are encountering the same issue.
We have all seen different articles and posts that detail the steps of how to embed a Canvas App within a Model-Driven form by adding the Canvas App control to a field on the form, but sometimes that might not be enough for the requirements that we have in place.
Recently, while working on a project that needed to update the Exchange rates in CDS, I was tasked at finding a solution that would be able to retrieve data from a SQL Server hosted on an Azure Virtual Machine. There were so many different approaches, and security was the main one, but I decided to do a deep dive and testing out how Power Automate will be able to accommodate these requests.
