Featured




Announcements
As outlined in the previous post, today we will build a canvas app! There are many great tools available to create a canvas app at the click of a button, including: Of course, we’ll not be using any of these options! Instead, we will be building o...
The very first post I wrote for this blog outlined why you should build a model-driven app. Now, after six months of writing about all the great things we can build with model-driven apps, we finally look at canvas apps! Canvas apps are already hu...
In our previous post we looked at Automated Flows, which are triggered in response to some other event. By contrast, Instant Flows are those triggered on demand. Examples of such flows include those triggered by: We will look into Canvas Apps and ...
In our previous post, we used a Scheduled Flow to send out a weekly email reminder. In this post we’ll look into Automated Flows – those that are triggered by some platform event occurring. In our LaRusso Autos, we will create Outlook calendar mee...
Many people don’t realise that the required user licenses for model-driven apps include Power Automate functionality in the cost, with the ability to run flows with premium functionality. This means that we can enhance our apps with automated work...
Every Dataverse enabled Power Platform environment has a User table. In any environment, the User table contains the records of all licensed Power Platform users in your Microsoft tenant who have access to that environment; if your environment has...
In this post, we conclude our series by importing all our application records – in our case, we are adding all the new Vehicles into our LaRusso Autos app. Along the course of this series, we’ve picked up many new skills including: This post will ...
At this stage in our series of posts, we’ve familiarised ourselves with: In the previous post, we added records to our Manufacturer table, using Power FX to assign random numbers for our Manufacturer Code column, which we defined as the Alternate ...