Latest blog posts
View allMany 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 ...
Having set out our plan in the previous post, we begin by importing data into our “Reference” tables. These are tables that: For our LaRusso Autos app, the Manufacturer table fits this criteria: In this post, we want to examine the data source and...
In our previous post, we introduced Dataflows and demonstrated how we can use them to create new records in bulk. However, that example was limited to creating data in a single table. What happens when we need to import data into multiple tables, ...
So far we’ve built two applications that allow us to create new records – our LaRusso Autos app allows us to create new records for Manufacturers, Models, Vehicles and Services. Our Dojo Membership app is much simpler as it only uses the Contact t...
All of the tables in our LaRusso Autos app have relationships with other tables, for example: Relationships like these are modeled as Lookup columns on our Dataverse tables, and when added to a Form, they look something like this: You can see here...