Manually Add Licensed Users in Dataverse Environment in Power Platform Admin Center

In case you want to reflect a recently licensed user in a Dataverse environment but you don’t see it reflect immediately, here’s how you can manually add users to the Dataverse environment yourself.

Check that the User has an appropriate license

From Microsoft 365 Admin Portal, ensure that the user has been successfully been given a license –

  1. In Users, click on the User and ensure the user has correct License required to be added to the environment.

  2. And even if you refresh the Enabled Users (in classic CRM UI), you don’t see the User.


    Here’s how you can quickly add a User instead of trying to sync all users (It’s possible to do that but slightly lengthy process). I’ll cover it in a separate post and link it here.
    First, let’s see in the below section on how to quickly add a User –

Add Users from Power Platform Admin Center

Given that you have the correct Dynamics 365 Administrator privileges, here’s how you can add Users manually –

  1. Go to the Environment in Power Platform Admin Center

  2. Go to the Users section once you expand on Users Permissions tab

  3. You’ll see that User is still not part of the environment. Here’s how you can add the User. Click on the + Add User button.

  4. Then, search for the User with their Email Address and you’ll see it populate once the user qualifies the criteria mentioned on the pane under User access requirements.

  5. Then, click on Add.

  6. In the next step, you’ll be asked to provide a Security Role to the User. For example, I’m assigning a Salesperson security role from the default Business Unit. And then clicking Save.

  7. This User will be added with the Security Roles. If you don’t see the name immediately, click on Refresh.

  8. You’ll see the User appear in the environment list.
    Also, you’ll see the User in the classic UI if you click on Manage users in Dynamics 365.

  9. Here’s how it’ll appear in the Classic UI.

Hope this was useful!

Thank you!

Enable Modern Controls for Canvas Apps in Power Platform

Now, Modern Controls have been recently announced, here’s how you can check them out.

Enable Modern Controls in Canvas Studio

By default, they are turned off, you need to explicitly enable them for your Canvas App.

  1. Modern Controls are not enabled by default as they are still in Preview as of the time of writing this post.
    Hence, you can see the Classic Insert menu as below.

  2. Open Settings in your Canvas App Studio editor

  3. Now, look for Experimental Features and look in the Preview section (You can also search ‘modern controls’ using the Search in this window to find the option quickly)

  4. Now, you can Save the app and do a full-page refresh if required. You’ll now see Modern Controls alongside the Classic ones in your Power Apps Editor.

Now, you can play along with these and test them out!

Microsoft Documentation on Modern Controls: Overview of modern controls in canvas apps (preview)

Thank you!

Configuring Power Apps Assets for Internal Documentation and help for Makers | Power Platform

As you organization grows, more developers join and look for help in order to get help on some of the best practices or advise on how to get the Apps developed the right way.

Power Apps Assets comes to rescue when finding important touch-points for sources of information within the organization.

Configure Power Apps Assets at the Org Level

Here’s how you can configure the Power Apps Assets at the Org level first in order to make them available for Makers in the environment –

  1. You can navigate to Power Platform Admin Center (https://admin.powerplatform.microsoft.com/) and expand Resources to find Power Apps assets

  2. Here, you’ll find that you can add links to Internal Resources and Advisors for the Power Apps.
    I can add Documentation, a Teams Group and a Yammer Community for Power Apps.
    Documentation – Ideally, you can add a link to a place where Makers should be able to find links to the best practices followed at the Org.

    Teams Group – You can have a Teams channel dedicated to helping Makers for any technical queries for new Makers.

    Yammer Community – You can make an internal community of Yammer and add link here so that Makers can reach out to Community for any help.

  3. Given that you know how to get links to these resources like getting the link to a Teams Group, SharePoint Repository and link to a Yammer Community, you can add these to the Power Apps Assets and save the Settings.

  4. Now, let’s add Advisors to the Advisors section. And you can add Advisors as shown below. Process is same as adding users to any area in Power Platform based on their Name/Email.

  5. Here, you have set the Power Apps Assets. Now, Makers are ready to utilize it.
    Here’s a post on how to enable Users for Power Apps Advisors: Enable yourself as a Power Apps Advisor

  6. Once a team member have made themselves for Advisor, they’ll show up as available in the list.

Utilizing Power Apps Assets

Now, that we have set the Power Apps Assets in the Power Apps Admin Center, we are ready to utilize the same. Given the scenario where the Makers are in a Canvas App building an App, here’s how they can utilize these resources –

  1. Example, Priyesh is logged in to Canvas Apps studio and needs help in starting the development process.

  2. Now, you’ll see a Power Virtual Agent in the Canvas Apps Studio, click on it to be able to access Power Apps assets.

  3. When you click on this button, you can enter some initial search term like Internal Resources. The bot will try to find anything matching your keywords.
    When it doesn’t find you can choose to not rephrase and let the bot give you other options to explore.

  4. Now, the bot will further ask you if you want to explore anything within the organization itself or not. Choose yes.

  5. When you click on yes, you’ll see the Power Apps assets show up.
    Also, an option to connect with an Advisor will be available.

  6. When you click on the links listed as Assets, they’ll open up the areas which you entered in Power Apps assets.

  7. Further, when you click on Advisor you’ll see which all Advisors are available to help you out.
    I had enabled CRM Admin user as an Advisor.
    So, the logged in user can choose to seek help from CRM Admin by sending them a message based on preferences set by the Advisor themselves when they made themselves available for advisory.

  8. Now, when you click on Send Message (given that the preference to reach out to advisor was set as Teams), a Teams message window will be opened for you to send in your message to them.
    You can send them a Teams message like you would for for any other user.

And that’s how Power Apps assets could help you out.

Hope this helps!

Thank you!

Enable yourself as a Power Apps Advisor

Now, Power Apps (https://make.powerapps.com/) allows you to make yourself available as an Advisor for other Power Apps makers –

Enable for Advisor Program (Preview)

Given that this feature is in preview at the time of writing this post –

  1. When signed into Power Apps Maker portal, you can expand the Settings pane and look for Power Apps settings.

  2. In Power Apps settings, you’ll find that a new section has been enabled.
    you’ll find that Advisor program is a new section (Preview at the time of writing this post). The default will be set to Not currently available since the program wouldn’t want it to be enabled for all by default and should be an opt-in.

  3. Now, once this enabled, you can choose if the mode of the communication should be Email or Microsoft Teams.

  4. Once you made yourself available for Advisory, you will be shown as Available in Advisors in the Power Apps Assets section.

This way, other Makers in the environment will be able to reach out to you in order to seek for help in their App making journey.

Hope this helps!

Thank you!

Enable Early Access Wave 1 2023 | Power Platform

Like every 6 months, enabling Early Access is one of the best things to look forward to as Microsoft announces Release Plans! So, here’s how you can enable Early Access for Wave 1 2023 if you are new to managing Power Platform environments!

It is recommended to enable Early Access features only for Sandbox environments as it is not GA [General Availability] yet.

Power Platform Admin Center

Given that you are a Power Platform Administrator / Dynamics 365 Administrator, here’s how you can enable Wave 1 2023 access for your Sandbox environment –

  1. Select the Sandbox environment



  2. Then, see the Updates section where you’ll now see 2021 Wave 1 updates available in Off mode.


  3. On the right hand side, you can select the U

  4. Then, enter the Display Name of the environment correctly in order to ensure you are enabling this on the correct environment.

  5. Once you confirm, you’ll see that the Updates have started applying in the background.

  6. And when you click or refresh, you’ll see what’s being Activated in the background based on how your environment is set up.

  7. It takes a few hours based on the environment for the Wave 1 2023 Updates to be applied.

And you’re set! Here’s Microsoft Learn Documentation for Wave 1 2023 for Power Platform / Dynamics 365: https://learn.microsoft.com/en-us/dynamics365/release-plans/?WT.mc_id=DX-MVP-5003911

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 Editable Grid using the New Power Apps Grid Control in Model-Driven Apps | [Preview]

If you are designing your forms in the Model-Driven Apps designer from the Power Apps Maker i.e. https://make.powerapps.com/, here’s how you can add the New Power Apps Grid (which is in Preview at the time of writing this post)

Scenario

For example, you are in Model Driven Apps designer and you are see the existing Grids, they have only 2 areas in Properties –

  1. Select the Grid and you’ll only see 2 areas –


  2. And if you expand them, you won’t find a way to change the control to, for example, Editable Grid.

  3. That’s where the new Power Apps Grid Control comes hand. This is currently in Preview at the time of writing this post.

New Power Apps Grid Control [Preview]

Now, click on the Components section to reveal all the Components that you could add to the Model-Driven Apps form –

  1. You’ll see the More Components section under which you’ll find the new Power Apps Grid Control.

  2. Now, once you drag is on the form where you want it to be, you’ll be asked to select the records it should hold. It’ll ask you to select the Table which you want to display in the sub-grid.

  3. Once you click on Done, make sure the Show Related Records is selected as well and ensure the Table and View selected is correct.

  4. Now, look for Components section and expand the same. Expanding the Components, you’ll be able to select the Editable Grid.
    Expand the Components section and you’ll find another button to add more components that are made available.

  5. Now, you’ll be able to select the Editable Grid here.

  6. Now that you have added Editable Grid, click Done.

  7. And once you add, you’ll notice that the Mobile, Web etc will be shown under the new grid. Means this is now set as default and not the other 2 views.

  8. Finally, you can save your changes and publish.
    And that’s how you are able to add Editable Grid on the modern Power Apps Model Apps designer using the new Power Apps Grid Component.

  9. And here’s how you’ll be able to add an Editable Grid on the Form using new Power Apps maker.

Here’s the Microsoft Learn link for the same – https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/the-power-apps-grid-control?WT.mc_id=DX-MVP-5003911

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!

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!