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!

App Access Checker in Power Platform Admin Center

Here’s how you can find if users have the correct access to a Model-Driven App assigned or not. This becomes the first line of troubleshooting when a Users say that they are not able to access an App.

Let’s see how to use this!

In order to check a Users’ access to a certain app, make sure you a Dynamics 365 Administrator and has access to the environment in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/environments)

App Access Checker

Here’s how you can check in the Power Platform Admin Center which user has the correct access to the Published Apps in Power Platform.

  1. Enter Settings by first selecting the desired environment where you want to check a User’s App Access.


  2. Then, look for Users.

  3. Alternatively, if you had clicked on the Environment name and entered the Properties, you’ll also find a Users link directly.



  4. Then, you’ll see the option for ‘app access checker’.

  5. Now, you’ll see a simple textbox which asks for the User ID of the user in the org whose access you are expecting to check.
    If you notice the URL, you can also bookmark this shortcut to your org’s name
    <a href="https://<orgName&gt;.crmhttps://<orgName>.crm<regionNumber>.dynamics.com/WebResources/msdyn_AppAccessChecker.html

  6. Once you enter and check, you’ll be able to see the status of the results.

  7. And you’ll see the details per app.

Hope this helps!

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!

Create Dataverse Virtual Table from SQL in Azure | Power Platform

Now, you can create a Dataverse virtual table by referencing a SQL Table. This is an easy way to bring in schema from your SQL Table in use and make it into a Dataverse Table.

Let’s see how.

Create SQL Connection Reference

First, let’s create an SQL Connection reference in Power Platform –

  1. Go to Connections, create a new Connection.

  2. Now, you can select the authentication type as SQL Server Authentication. You can choose based on how your setup is, but if you want to quickly test this feature, you can follow this process.

  3. Then, you need to fill in the Server Name and Database Name.
    You can get the Server Name from here in the Azure Portal. You’ll find a Server name in the SQL Server details.

  4. And Database Name under the Server itself as

  5. And fill out the information as below.

  6. Further, if you scroll, you’ll need Server Admin name which will be on the Server itself.

  7. And fill the same in the fields below in the connection dialog box. Finally, click Create.

  8. Connection is now created.

Create Table

Here’s how you can create a virtual Table in Power Apps Maker (https://make.powerapps.com/) –

  1. Once you are in Power Apps Maker, go to Tables and you can drop down from Create Table menu.

  2. You’ll see option to Create by connecting to external source.

  3. Now, you have 2 options at this point of writing this blog. One is SQL and other is SharePoint. We’ll select SQL for this example. Both also use the connection you are logged in.
    You can select the connection we created in the steps above.

  4. In the next step, you’ll see the Tables from SQL. In this example, our table is student.

  5. When you click Next, you’ll see the columns from SQL

  6. Once everything looks good, you can then click Next. Finally, you’ll see he summary of the Dataverse virtual table to be created.

  7. And finally, the Table will read the data from SQL and display here. The data will not be synced back to SQL.


In case you also want to know how to convert a SharePoint list to Dataverse table, you can refer this post – Create Dataverse Virtual Table from SharePoint List | Power Platform

Hope this helps!

Thank you!

Create Dataverse Virtual Table from SharePoint List | Power Platform

Now, you can create a Dataverse virtual table by referencing a SharePoint List. This is an easy way to bring in schema from your SharePoint List in use and make it into a Dataverse Table.

Good news is that this also syncs back to the SharePoint List! Let’s see how.

SharePoint List

Let’s say you have a SharePoint List which you want to convert into a Dataverse Table in your Power Platform –

Let’s do this by creating using a Virtual Table which now connects to SharePoint and SQL. Please note that at the time of writing this post, connecting to external data is still in Preview.

Create Table

Here’s how you can create a virtual Table in Power Apps Maker (https://make.powerapps.com) –

  1. Once you are in Power Apps Maker, go to Tables and you can drop down from Create Table menu.

  2. You’ll see and option to Create by connecting to external source.

  3. Now, you have 2 options at this point of writing this blog. One is SQL and other is SharePoint. We’ll select SharePoint for this example. Both also use the connection you are logged in.

  4. Once you select SharePoint, you’ll either be asked to select one of the recently used Sites or if you know the URL of the Site in which your list resides, you can choose the same.
    Refer below that I’m choosing up to the name of the Sub-site in question.

  5. So, you can either select a recently used Site or just paste the URL of the Site which has your List in it.


    OR


  6. Once you are in the desired Site, you’ll see the List under that Site.

  7. Once I select the List, I’ll be asked if I need to change any schema name from the ones identified by the wizard.

  8. Or if everything looks OK, you can simply click on Next. You’ll be given a summary of what Table will be created from your SharePoint list.

  9. It takes a few moments to create this Virtual Table for you with the data from the SharePoint List.
    Once ready, it’ll appear as below with the data and you can start adding your data as well.

  10. Also, the data you add from the Virtual Table is also sent back to the SharePoint List.

  11. This entity / table will be listed as any other Table in the Power Apps Maker with the Virtual type.


Hope this helps!

Thank you!

Environment Assignment settings in Power Platform Admin Center

Environment Assignments and who should be able to create what types of Dynamics 365 CRM / CE / Dataverse environments can now be easily controlled.

You can either let everyone create a certain Type of environment or only enable Admin groups to create environments in Power Platform Admin Center! Let’s see how.

Restricting Users from Creating Environments

You can now restrict which types of Environments are allowed to be created for the type of audience in your tenant –

  1. If you are one of the Global Admins, Power Platform Admins, you have access to the Power Platform Admin Center settings (https://admin.powerplatform.microsoft.com/tenantsettings)
    And you’ll see the below types of Environment Assignments available for you to tweak
    Developer environment
    Production environment
    Trial environment
    Add-on capacity


  2. And in this example, let review and modify the settings for Production types of instances and who should be able to create this environments.
    Every type of assignment will have the below 2 options –
    Everyone
    Only specific admins (Global Admins, Power Platform Service Admins & Delegated Admins)
    Reference Link: https://learn.microsoft.com/en-gb/power-platform/admin/control-environment-creation?WT.mc_id=ppac_inproduct_settings?WT.mc_id=DX-MVP-5003911


  3. Once your preferences are set, just click on Save and the settings will be applied. Let’s see in the next section how this works.

Restriction Imposed

Here’s how a User will be restricted when they try to create the Types of environments when they are not part of the Admin Groups –

  1. Although, every user will get an option to Create using the Create button and select a Type of environment. When a User selects a Type, in this case Production

  2. And when they click Next, and enter further details in order to create the environment, they’ll see this error message.

  3. And to validate, you can look at the Roles in Microsoft 365 Admin Center under Users as to what Roles they have been assigned with.

Hope this helps!

Identify deprecated JS code in your Power Platform solution using Solution Checker

Recently, you must’ve received an intimation from Microsoft saying that ODATA v2 is now deprecated. See this link: https://powerapps.microsoft.com/en-us/blog/odata-v2-0-service-removal-date-announcement/

And if you are wondering how to go about finding what has been used, you can use Solution Checker to identify deprecated code which should show up like below using your Solution Checker.

Let’s see how we can use Solution Checker!

Running Solution Checker

Here’s how you can run Solution Checker in Power Apps Maker Portal (https://make.powerapps.com/) and see the results –

  1. Given that your solution already contains the JS Web Resources which you want to run Solution Checker on, you can select the Solution and expand Solution Checker to click Run as shown below.

  2. It takes a few moments to Run the Solution Checker solution. You’ll see the spinner as shown below.

  3. Once completed, you can expand the Solution checker and click on View Results.

  4. Once you click on View Results, you’ll see the list of detected anomalies in your JS Web Resources.
    Apart from the suggested JS best practices, you can see the Category Upgrade Readiness to identify the deprecated code being used in your solutions.

  5. Once you click on the Reference link in each of these results, it’ll open up a Pane on the right hand side to show what the issue is

  6. And when you click on Get the complete guide, here’s the link of the same (https://learn.microsoft.com/en-gb/power-apps/maker/data-platform/powerapps-checker/rules/web/avoid-2011-api?WT.mc_id=DX-MVP-5003911) which will give you the below details in Microsoft Learn Documentation –

  7. Now, if you look at the code that is being references in the Solution Checker result, you’ll see the old code (marked with Red Box)being used.
    Instead, you should use the new code (marked with Green Box) to do carry out the newer version of the functionality –

  8. See the next section in this blog to get the details on the deprecation in client side scripting for Power Platform / Dynamics 365 CRM.

Important Deprecations for Power Apps & Power Automate

Here’ are the Deprecated APIs for Power Platform / Dynamics 365 CRM Client Scripting: https://learn.microsoft.com/en-us/power-platform/important-changes-coming#some-client-apis-are-deprecated?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

Power Apps Developer Plan environments | Power Platform

Developers can now have Environments of their own to test and review Power Apps / Power Automate etc. Here’s how you can get yours!

Learn More about Power Apps Developer: https://learn.microsoft.com/en-us/power-apps/maker/developer-plan?WT.mc_id=DX-MVP-5003911

If you are looking to Sign Up for the Developer Plan, you can use this Link: https://powerapps.microsoft.com/en-us/developerplan/?WT.mc_id=DX-MVP-5003911

Create Developer Environment

Given that you are Power Platform Admin Center, you can create a new Environment like so –

  1. Go to Power Platform Admin Center and then Environments (https://admin.powerplatform.microsoft.com/environments). Click on + New to create a new Environment.



    And then you can select the Type

  2. Now, can you check what URL you want to provide and then click on Finish

  3. Then, your environment will be initiated for creation like any other Environment. Notice the type is Developer.

  4. Once created, if you go in the Environment, you can click the Edit to review the Settings for this Environment.

  5. And you can see that the Security Group cannot be added to this Environment.

User’s Environment

  1. If a User wants to create their own environment under the Power App Developer Plan (https://powerapps.microsoft.com/en-us/developerplan/?WT.mc_id=DX-MVP-5003911), they can go to the Homepage of the Power Apps Developer plan and click on Existing User? Add a dev environment >

  2. Then, you can enter your credentials and you’ll see this page.

  3. Once this is provisioned, you’ll be taken to your Environment and I’ll look like below –



  4. And in the Power Platform Admin Center, the Admins can see that the Environment has been created of Type Developer by SYSTEM.

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!

Weekly Digest for usage insights | Power Platform Admin Center

One of the features in Power Platform Admin Center is that now you can receive Weekly Updates in the form of a Newsletter for the Managed Environments.

Pre-Requisites

Below are the Pre-requisites for enabling Weekly Digest

  1. Tenant-Level Analytics must be enabled in your Power Platform Tenant. Here’s a post to see how you can enable Tenant-Level Analytics – Tenant-Level Analytics in Power Platform Admin Center | For Power Apps and Power Automate
  2. Only Managed Environments Updates are available – Here’s how you can learn more about Managed Environments – Enable Managed Environments in Power Platform Admin Center
  3. Under those Managed Environments, only those Managed Environments will be considered which have been enabled for Weekly Digest. While enabling Managed Environments in the above step #2, ensure this checkbox is marked in order to consider the Managed Environment for Weekly Digest –

Enable Weekly Digest

Given the above Pre-requisites are met, here’s how you can enable Weekly Digest –

  1. Navigate to Tenant Settings in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/tenantsettings) – Look for Weekly digest. Notice that it is marked with a green icon which indicates that it will only be applicable for Managed Environments.

  2. On the right hand side, you’ll see place to enter email addresses (separated by semicolons) who should receive the Weekly Digest emails.
    Power Platform Administrators and Dynamics 365 Administrators only will receive these updates.

  3. Once you entered the email addresses, you can Save those and you’ll see the below message upon confirmation.

  4. That’s it!
  5. And then on a Monday, I saw this in my mailbox!

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!