Setting up Billing Policy for Dataverse Environments in Power Platform for Azure Pay-As-You-Go plan | Microsoft Azure

Pay-as-you-go has been recently announced with Azure and I too wanted to explore this topic myself on my trials Dataverse/D365 Sales environment as well as my Microsoft Azure trial subscription which I started.

Disclaimer: Please note that I’m exploring this topic and sharing as I go on. Hence, I’ll continue to write further topics as I proceed. Please try on your Dataverse trial & Microsoft Azure trial subscription to identify / estimate the costs your actual implementation will incur.

I also recommend going through the below Microsoft Learn Pages for detailed information on pricing and meters of the Pay-as-you-go model –

Detailed Microsoft Docs for Pay-as-you-go: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-overview?WT.mc_id=DX-MVP-5003911

Power Apps Pricing: https://powerapps.microsoft.com/en-us/pricing/

Pay-as-you-go Meters: https://learn.microsoft.com/en-us/power-platform/admin/pay-as-you-go-meters?tabs=image?WT.mc_id=DX-MVP-5003911

Let’s see how we can get started!

Setting up Billing Policy

Here’s how you create Billing Policy in Power Platform –

  1. In Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), you can see Policies section. If you expand the same, you can see Billing Policies.

  2. Here, you can start by creating a new Billing Policy

  3. You can give it an appropriate name. And it doesn’t allow you to have spaces.

  4. Next, you’ll be asked to select the Subscription you wan to assign the Billing Policy under.
    Notice the error below. My Free Trial Azure Subscription doesn’t have a Resource Group created yet. Hence, this need to be present.


  5. Since at this point, I don’t have a Resource Group under the Azure Subscription I selected, I need to go to Azure Portal (https://portal.azure.com/), search for Resource Groups

  6. Since you might not have any Resource Group right away, you can create one.


  7. I’ll just give it a name which I can identify with.


  8. I’ll validate and Create the same in Azure.


  9. Resource Group will be created here.


  10. Now, when I come back to Power Platform, if I reselect the Azure Subscription, I’ll now see that the Resource Group I created is showing up.

  11. I’ll select the same and select United States as the Region.
    And click on Next.


  12. In the next steps, I can select which all Environments should be included in the Policy. Then, I can click on + Add to policy.

  13. You can see the Added to policy tab now showing your environment. Once you are satisfied with the selection, you can click on Next.

  14. Final step is to now Review and confirm the policy you are creating.

  15. It’ll take a moment to start provisioning. Then, you’ll see the status as Provisioning.

  16. Once completed, the status will show as Enabled.


  17. Now, when you go back to Azure Portal and open the Resource Group, you’ll find a Deployment show up



  18. Open it up and you’ll see a Deployment created.

  19. And if you open the Deployment, you can see the DataverseBilling which we had set up in Power Platform.


  20. And this point, you are now setup with using Pay-As-you-go plan for your Dataverse environment(s).

    Note: Further, I’ll write follow up posts as I explore Pay-as-you-go scenarios and experience myself.

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform\
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Adding Image field on the form in Dynamics 365 CRM | Power Platform Modern Form Designer [Quick Tip]

If you are predominantly working in Dynamics 365 CRM i.e. the classic Form Designer and have one of the below fields –

You won’t be able to find it to add it on the Form in the Classic Editor.

And you are wondering how you can get this field on the form, then this quick tip is for you!

Modern Form Designer

Given that you are aware of how to get to the modern form designer –

  1. Once you open the Form from Power Apps (https://make.powerapps.com/), you can go to the Solution your Form/Fields are put in.


  2. Then, open your Form from the Solution

  3. And in your Form, if you look for the fields / Columns section to put on the form, you can see the Thumbnail field we created is present.

  4. You can then double click it and add on the Form. And then, this field will also work when using Dynamics 365 CRM Apps like Field Service, Sales etc.

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. Blocking Attachment Extensions in Dynamics 365 CRM
  2. Upgrade Dataverse for Teams Environment to Dataverse Environment
  3. Showing Sandbox or Non Production Apps in Power App mobile app
  4. Create a Power Apps Per User Plan Trial | Dataverse environment
  5. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  6. Co-presence in Power Automate | Multiple users working on a Flow
  7. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  8. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  9. Call a Flow from Canvas Power App and get back response | Power Platform\
  10. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  11. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  12. Asynchronous HTTP Response from a Flow | Power Automate
  13. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  14. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Users cannot create Flows in Power Automate | Environment Maker permissions

If you are someone who has been asked to create Flows in Power Automate, and you go to Power Automate portal (https://make.powerautomate.com/) to make your first Flow in your environment, you may come across this if you are not an Administrator yet –

The error message would say -“You are not permitted to make flows in this ‘<EnvironmentName>’. Please switch to the default environment, or to one of your own environment(s), where you have maker permissions.

Now, let’s see what the issue is about.

Environment Maker Permissions

As a Power Platform Administrator yourself, you’ll need to provide Environment Maker privileges (Security Role) to the affected User in your environment –

  1. Navigate to the the Settings for the Environment in PPAC (https://admin.powerplatform.microsoft.com/)
    And look for Security Roles in Access area –

  2. Look for the Environment Maker role.

  3. When in Environment Maker role, look for the Add People button on the top.

  4. Now, search for the user who should have the Environment Maker permissions and click Add (which will be at the bottom of the pane).

  5. Now, you’ll see that this user is added.

  6. Now, when the User will refresh the Flow Editor, they’ll no longer see the error message and will be able to create/save Flows.

Hope this was useful!

Here are some Power Automate posts you want to check out –

  1. Blocking Attachment Extensions in Dynamics 365 CRM
  2. Upgrade Dataverse for Teams Environment to Dataverse Environment
  3. Showing Sandbox or Non Production Apps in Power App mobile app
  4. Create a Power Apps Per User Plan Trial | Dataverse environment
  5. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  6. Co-presence in Power Automate | Multiple users working on a Flow
  7. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  8. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  9. Call a Flow from Canvas Power App and get back response | Power Platform\
  10. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  11. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  12. Asynchronous HTTP Response from a Flow | Power Automate
  13. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  14. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Enable Power Automate Pane in Canvas Apps Studio | Preview

Now, you can start creating Flows from within the Power Apps itself and add Power Automate as a Pane on the left hand navigation.

Let’s check out how –

Enable Power Automate Pane

In the App Studio, here’s how you can turn on the Power Automate pane –

  1. In the App Studio, you can see the Settings button, clicking on which will open up the Settings area.
    Go to Upcoming Features tab and look at the Preview section since this feature is still in Preview.

    You’ll find the Enable Power Automate pane option turned off by default.

  2. Before you turn it on, you’ll see the left hand menu doesn’t have a Power Automate icon/section added already.

  3. And when you Turn it On, you’ll see the Power Automate section added.

  4. Now, when you expand it, it appears like you can create a Flow from here.

  5. When you click on Create new Flow, you’ll get the option to start creating from a Template or create a new one like you usually do in Power Automate app itself.

  6. I clicked on Create from blank in the above step, you’ll then get the Flow editor right there and PowerApps as the trigger since this will be triggered from your Canvas Power Apps.

  7. Now, you can continue to build you Flow and once done, it’ll be available in the list to be used.

  8. And you can then use this Flow as per requirement.

Existing vs New Method

Let’s see the subtle difference between the existing and the new method -1

  1. Once you enable this, you’ll find 2 Power Automate buttons (Perhaps this will change in the near future)
    Once will open the new pane and the other existing one will open in the old way in context of the Screen being used.

  2. Additionally, the existing method will open the Power Automate portal itself in the new tab as opposed to opening the Flow in the Canvas Apps Studio itself.

Hope this helps!

Here are some Power Automate posts you want to check out –

  1. Showing Sandbox or Non Production Apps in Power App mobile app
  2. Create a Power Apps Per User Plan Trial | Dataverse environment
  3. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  4. Co-presence in Power Automate | Multiple users working on a Flow
  5. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  6. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  7. Call a Flow from Canvas Power App and get back response | Power Platform\
  8. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  9. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  10. Asynchronous HTTP Response from a Flow | Power Automate
  11. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  12. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Create a Flyout menu for ribbons in Ribbon Workbench | XrmToolBox

Here’s how you can create Flyout menu in Ribbon Workbench.
Also, for most ribbon customization, you can edit using the Command Editor in Power Apps but this is in Preview at the time of writing this post –

  1. How to add low-code Power Fx buttons to model-driven apps (Commanding v2) – https://www.develop1.net/public/post/2021/07/25/commandingv2
  2. Comparison between Ribbon Workbench and Power Fx Command Buttons –
    https://www.develop1.net/public/post/2021/07/25/RibbonWorkbench-vs-PowerFx

Meanwhile, here’s how you can create a Flyout menu in Dynamics 365 CRM Ribbon using Ribbon Workbench in the XrmToolBox

Ribbon Workbench in XrmToolBox

In classic XrmToolBox style, here’s how you create a Flyout button. Given that you are aware of how to load the Entity’s ribbon in a solution and then onto the Ribbon Workbench, we’ll see at how we can create a button on Account Form –

  1. Insert the Flyout menu in the Ribbon where you want to insert this. In this case, in the Form ribbon of the Account entity.

  2. Once dragged, pick a Menu Section control and insert into the flyout canvas shown in screenshot below. Because all the Buttons will fall under that Buttons can’t be added directly into the Flyout menu.

  3. Now, you can name the Menu Section itself as show below –
    Note: In case if you named the Section correctly and it didn’t appear the first time, clicking on some other component and then clicking it back will show it correctly.

  4. Now, you can insert buttons underneath the section. In this case, I’ll add 2 buttons for Pause and Cancel.


  5. Make sure you populate the Command and the ModernImage icon for it’s icon so that the buttons are visible when you publish. Without a Command being attached to the Button, the button will not be visible.
    The final button layout will look like this.
    Note: In case if you named the Section correctly and it didn’t appear the first time, clicking on some other component and then clicking it back will show it correctly.

  6. Once ready, publish the changes and see. Your Flyout menu will be ready and will look like this!

Hope this was useful!

Here are some more XrmToolBox related posts which you might want to check –

  1. Show custom ribbon button based on Security Role of the logged in User in Dynamics 365 | Ribbon Workbench in XrmToolbox
  2. Connecting XrmToolBox to an MFA enabled Dynamics 365 environment | Azure AD
  3. Find deprecated JS code used in your Dynamics 365 environment | Dynamics 365 v9 JS Validator tool | XrmToolBox
  4. Delete App Passwords created by other users in Office 365 | Multi-factor authentication
  5. Single record and multiple record auditing in Dynamics 365 to Audit record access | M365 Compliance
  6. Filter records in a View owned by a Team you are a member of | Dynamics 365 CRM
  7. Show custom ribbon button based on Security Role of the logged in User in Dynamics 365 | Ribbon Workbench in XrmToolbox
  8. Ribbon button visibility based on a field value in Dynamics 365 | Ribbon Workbench
  9. Get GUID of the current View in Dynamics 365 CRM JS from ribbon button | Ribbon Workbench
  10. Pass Execution Context to JS Script function as a parameter from a Ribbon button in Dynamics 365 | Ribbon Workbench

Thank you!

Install On-Premise Gateway from Power Automate or Power Apps | Power Platform

Here’s your summary to understand what are On-Prem Gateways in Power Automate and how you can set them up.
The same can be done from Power Apps as well (https://make.powerapps.com/)



So let’s see how you can set it up and get started. This post is for beginners who are looking to install an on-premise gateway. So this should be fairly simple process! 😊

Create an On-Prem Gateway in Power Automate

Here’s how you can create an On-Prem Gateway in Power Automate

  1. Expand the Data section and look for Gateways. Then, when you go in Gateways, you will see + New gateway button.


  2. Then, you’ll be taken to a new webpage (https://powerapps.microsoft.com/en-gb/downloads/). Here’s you’ll be able to Download an on-prem Gateway

  3. Once you click on Download, it’ll start downloading the Installer on your machine.


    It’ll complete, then you can simply open it to start installing.

  4. Once you begin the installation, choose where the Gateway folder path should be.
    Then, click Install.


    And it’ll install and will take a few moments.
  5. Once completed, it’ll ask for the email address (or rather username needed to install the Gateway)


  6. Further, authentication will take place as below (in case you have MFA enabled, that will be occur too)


  7. And, it’ll Sign you in.

  8. Once in, it’ll ask if this is a migration or the first time setup.
    Since I’m installing it for the first time, I’ll choose the first option as this is a fresh install.

  9. Upon clicking Next, I’ll be asked to set Properties for the gateway.
    So, to identify the machine, I’ll select a name with which I can identify and then enter a Recovery Key which I will store safely with me.
    Then, click Configure.


  10. It’ll take a few moments to configure.




  11. And now, you’re done in a few moments. Finally, the Gateway is now installed.


Configuration & Info

Given that your Gateway is now installed, you can always go in the File Explorer where you set it up and open the below app

If you wish to check the configurations in detail, you’ll need to Sign In again

And in Power Automate, you’ll see the Gateway is listed.


And if you open it up, you’ll see the high-level details and status of it.

Here are some Power Automate posts you want to check out –

  1. Co-presence in Power Automate | Multiple users working on a Flow
  2. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  3. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  4. Call a Flow from Canvas Power App and get back response | Power Platform\
  5. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  6. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  7. Asynchronous HTTP Response from a Flow | Power Automate
  8. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  9. Converting JSON to XML and XML to JSON in a Flow | Power Automate
  10. Duration field in Dynamics 365 converts Hours value to Days in Dynamics 365 | [Flow Workaround to convert in Hours and Mins]

Thank you!

Column dependency for Event Handlers for Model-Driven Apps – Modern vs Classic form designer | Power Apps Tip

You must be already familiar with Locking fields on the form in Dynamics 356 CRM so that they are not removed from the form unless you remove the Lock.

Also, it’s a “best practice” to add Dependencies explicitly to your events so that if multiple customers are working on the same form, no one should delete a field which is required by Events added to fields/forms.

In the modern form designer, it looks like below


And when you try to remove the field from the form, you’ll see this error.

Now, there’s also another way you can lock this field and not remove it explicitly due to a dependency – Let’s see what we have in the modern app designer!!

Events dependency in modern app designer

Let’s say you are using the modern app designer to work on your forms, here’s what you notice

  1. For example, you are using the modern App Designer and you are working on Website field on the Account entity.
    Let’s add an Event Handler for the Website field in the modern designer.

  2. Once you added an event, you’ll see a Column Dependency field which can choose to select fields. (Denoted by arrow in below screenshot)

  3. Here, I’ll select the Website field from the dropdown so that the Lock is established on the field.

  4. So now, when I look at the field Properties, the Lock will be disabled and I can’t choose to remove it explicitly from the Properties itself.


In Classic Form Editor

Here’s where you can add dependencies to Event Handlers in the Classic Form Editors (I’ll be honest, this usually goes unnoticed and I never cared to add dependency)

  1. Wherever you add Events on the field/form, look for the Dependencies tab on the window where you add the JS function.


  2. And you’ll see the fields which are selected for Dependencies so that they are not accidentally removed.

Here are some more Power Apps related posts you might want to check out –

  1. HTML Text control in Canvas Power Apps | Power Platform
  2. Configure Dataverse Search in Power Platform Admin Center | Dynamics 365
  3. Form Access Checker in new Power Apps Form Designer | Model-Driven Apps in Dynamics 365
  4. Log Canvas Power App telemetry data in Azure Application Insights | Power Apps
  5. Variables in Canvas Power Apps | Global and Context
  6. Dynamics 365 Solutions’ New Experience in Power Apps, Solution Checker and more
  7. Navigate Screen automatically based on Timer in Canvas Power App | Power Platform
  8. Advanced Lookup in Model-Driven Apps | Power Platform
  9. New App Designer for Model-Driven Apps | Power Platform
  10. Primary Key of Activity type entity in a Dataverse connector in Power Automate | Quick Tip

Thank you!

Create a Power Apps Per User Plan Trial | Dataverse environment

Here’s how you can create a Power Apps trial under the Per App Plan which is of $20!
Link: https://powerapps.microsoft.com/en-us/pricing/

Under Per App Pricing, look for Try New button where you can start the trial setup process.

Setting up a new tenant

Once you use the above link to, you’ll be taken to the Setup page like any other Dynamics trials you must’ve signed-up for –

  1. Fill in an email on which you would want to receive subscription communication email.
    Then, click Next.
  2. In the next step, if the email address doesn’t exist ()-

  3. Next, under Tell us about yourself section, enter the basic details.

  4. Once you fill in these details, click Next. You’ll be asked to enter phone on which you’ll receive the OTP to authenticate

  5. Enter code and proceed.
    In case you want to change the domain, you can do so before finalizing. Else, you can directly click on Next.


    And once this is finalized, you can click on Save and it’ll be locked.
    So in case you changed, then click on Next post that.

  6. In the final step, you’ll see the below. Once the info is correct, click on Get Started and you’ll be taken to M365 Admin Portal.

License

If you check the license which is assigned in this, you’ll see the –

Creating a Dataverse Environment

Now, you can create a Power Apps Dataverse environment –

  1. Go to https://admin.powerplatform.microsoft.com/ and you can click on New.

  2. Now, you can set the name of the environment.
    Note that the default type is set to Sandbox [I’ll tell you why this will cause an issue]


  3. In case you proceed to create a Sandbox type


  4. You’ll end up having this error which needs at least 1GB space.

  5. That’s why you can go back and change the Type to Trial (Subscription-based).
    Also, notice that the Database will be created.

  6. Then, you can proceed. Also, notice that I’m also deploying sample data. Hence, Power Apps based Apps will be setup with demo data and not the Dynamics 365 Apps.

  7. Then, provisioning will start.

  8. In a few moments, the environment will be created and you can navigate to it.

  9. Select the environment and click on Open Environment.

  10. And the environment with sample apps and data will open up!

Here are some more Power Apps related posts you might want to check out –

  1. HTML Text control in Canvas Power Apps | Power Platform
  2. Configure Dataverse Search in Power Platform Admin Center | Dynamics 365
  3. Form Access Checker in new Power Apps Form Designer | Model-Driven Apps in Dynamics 365
  4. Log Canvas Power App telemetry data in Azure Application Insights | Power Apps
  5. Variables in Canvas Power Apps | Global and Context
  6. Dynamics 365 Solutions’ New Experience in Power Apps, Solution Checker and more
  7. Navigate Screen automatically based on Timer in Canvas Power App | Power Platform
  8. Advanced Lookup in Model-Driven Apps | Power Platform
  9. New App Designer for Model-Driven Apps | Power Platform
  10. Primary Key of Activity type entity in a Dataverse connector in Power Automate | Quick Tip

Thank you!

Configure Dataverse Search in Power Platform Admin Center | Dynamics 365

Relevance Search in Dynamics 365 CRM recently got renamed to “Dataverse Seach” as you might have seen some updates.

Here’s how to configure the Dataverse Seach in the new Solutions Explorer!

Scenario

Now, in case you search on the Global Search bar for a record and the table which it lies in doesn’t show up – In this case table I’m looking in is ‘Subscription’ – that means that this entity is not configured for Dataverse Search

Dataverse Search

Here are some points on the Dataverse Search –

  1. Dataverse search is enabled directly is you are opted in to 2021 Wave 2 Updates on your environment.
    Go to https://admin.powerplatform.microsoft.com/ and open the desired environment’s Features section from Settings.


    You’ll find that Dataverse Search is already ON.



  2. Now, navigate to https://make.powerapps.com/ to configure the Dataverse Search for a specific entity.
    Go to Solutions and look for the Solution which has your entity
    In this example, I’ll use the custom entity I’ve created called as ‘Subscription’

  3. In any solution which has this entity, I can click on Overview on the left.


    And then if you look at the right hand side – click on Manage Index


  4. It’ll show the entity which is not enabled for Search – But, notice that it is unchecked – means it is not enabled.



    Now, enable and save it




Check if Table is enabled for Dataverse Search

  1. Enable the Table for Search Results. Now, when you are in the Solution in the new Solution Explorer – Look for the Table. In my example, it is Subscription table.
    I’ll open the Settings of the Table.


  2. In the Settings of the Subscription table, you’ll need to expand the Advanced options.


  3. Now, scroll below and you’ll see the option for Appear in Search Results is enabled.



  4. And once this is enabled, the results will show up in Dynamics 365

Indexed Columns

Now, here’s how to understand the count of Indexed columns. Limit of 950 columns is imposed in a Dynamics 365 environment.
Refer Microsoft’s Official Post – https://docs.microsoft.com/en-us/power-platform/admin/configure-relevance-search-organization#select-tables-for-dataverse-search?WT.mc_id=DX-MVP-5003911

  1. Here’s a snippet from the above mentioned Microsoft Docs to show the count of Indexed Columns calculated towards a Dataverse Search

Hope this helped!

Here are some more Canvas Power Apps posts you might want to check –

  1. Transition effect on Gallery Items when hovered over in a Canvas Power App | [Quick Tip]
  2. Navigate Screen automatically based on Timer in Canvas Power App | Power Platform
  3. Search on multiple columns from a Dataverse table in a Canvas Power App Gallery control | Power Platform
  4. Call a Flow from Canvas Power App and get back response | Power Platform
  5. Enable Custom Code Components (PCF Controls) to be imported in a Canvas Power App | Quick Tip
  6. Retrieve Hashtags from Text in a Canvas Power App | Power Platform
  7. Rich Text Control for Canvas and Model-Driven App | Quick Tip
  8. Setting Correct Default Mode for Forms in a Canvas App | [Quick Tip]
  9. Rating Control to represent data from Dataverse in a Canvas Power App | Power Platform
  10. Clear a field value & Reset Form in a Canvas Power App [Quick Tip]
  11. Get Dynamics 365 field metadata in a Canvas App using DataSourceInfo function | Common Data Service
  12. Implement character length validation in a Canvas Power App | Power Platform

Thank you!

New App Designer for Model-Driven Apps | Power Platform

The new Model Driven App Designer experience has been enabled and has been doing the rounds for a few days now. Here’s my take on the same to demystify and bring forward a quick example of a Model-Driven App capabilities.

I’ll keep enriching this post in the future as more enhancements come to this new experience! As of now, this is in preview, so kindly keep a note of that!

Let’s review further!

Create a new Model-Driven App

Here’s how you go about creating the new Model-Driven App using the new App Designer –

  1. In your https://make.powerapps.com/ portal, create a new Solution and then go inside the Solution to create a New Model Driven App as shown below




  2. Then, select the Modern App Designer (Preview)


    And give it a suitable name.

Editing the SiteMap in the New Model App Designer

Here’s how you go about adding new Entities to the SiteMap in the new Model App Designer experience. Navigation section

  1. I can click on New Page to start adding my first Page. Out of a Dashboard and Table, I’ve chosen to add a Table.


  2. Now, if you look at the right hand-side of the page, you should be able to select what you want to add here.




    And I’ll select Account Table.



  3. I’ll also rename the Title to to Customers.


  4. Now, I look at the left hand side, my App begins to take shape and I can then also change the Group and Area names like you would do in a Site Map.

  5. I’ve also renamed the Area to Sales now.





Pages

Now, let’s see what all Components can be added to the App. Pages is where you can either add Entities directly or edit the ones which you added in the Navigation section above.

  1. Now, if you go to the Pages section, you’ll be able to expand into the navigation and choose the components yourself.

  2. Now, if you select the Account form (as selected in the step above), look on the right hand side to be able to select which all Forms you want to add to the App. If you don’t select anything, all forms will be selected by default.


  3. Now, let’s select a couple of Forms.


    And those will be added.


  4. Same goes for Views as well. I’ve added 2 Views as shown below



    Note: Ideally, the WYSIWYG Preview should show only the components I added, but it shows me everything. Perhaps, this is work in progress.


    Along with that, there are Known Limitations at this point since this is in Preview.
    https://docs.microsoft.com/en-gb/powerapps/maker/model-driven-apps/app-designer-overview?WT.mc_id=DX-MVP-5003911#known-limitations


Data

Also, if you expand data, as of now only the ones added to you app is shown. Nothing much happens here. I’ll update this area once more features are added in the near future.

Hope this post was useful!

Here are some more useful posts you might want to check –

  1. Rich Text Control for Canvas and Model-Driven App | Quick Tip
  2. Form Access Checker in new Power Apps Form Designer | Model-Driven Apps in Dynamics 365
  3. How to add Rating Values to Rating Models in D365 Field Service and PSA
  4. D365 Quick Tip: Simple & Detailed Mode in Advanced Find
  5. Language format for Whole Number field in Dynamics 365 CE
  6. Transition effect on Gallery Items when hovered over in a Canvas Power App | [Quick Tip]
  7. Filter records in a View owned by a Team you are a member of | Dynamics 365 CRM
  8. Change Booking Status colors on Schedule Board for Field Service/PSA [Quick Tip]
  9. Change the Unified Interface App Icons
  10. Custom Help Pages and Guided Tasks for Unified Interface in Dynamics 365

Thank you!