Use Monitor to debug Model-driven apps remotely | Power Platform

March 18, 2024 priyeshwagh777 Microsoft PowerApps, Power Platform Admin Center Dataverse, debug monitor, debug monitor model driven power apps, debug monitor power apps, Dynamics 365, monitor in model driven apps, monitor in power platform, power apps, Power Automate, Power Platform

Monitor is one feature that comes in super handy when end-users complain about an issue which is difficult to ask end users to send across logs from the browser.

And here’s where Monitor comes in handy!
Let’s see how this works through this simple blog post!!

Capture events from Monitor in Model Driven Apps

Here’s how you can Monitor in Model-driven apps’ Monitor to capture issues on an End User

You can go to Power Apps Maker Portal (https://make.powerapps.com/) and make sure you are switched to the intended environment.
Then, select Apps on the left hand pane and expose all the Apps. Select the Model-Driven app you want to enable Monitor for. Once you select, you can then drop down from Details flyout menu and click on Monitor.
Once you click on Monitor, it opens the Monitor application itself where all the logs you work on will be captured. And you can also notice that there’s a Play model-driven app button as well to enter in Debug mode.
It opens the Model-driven app in a new tab and asks you to confirm if you want to join the debug session.
Once you click on Join, it’ll run the app in debug mode and you can see the Monitor tab and notice that it has started capturing the logs based on your operations in the Model-driven app session you are running in parallel.
And when you go about working in the model-driven app, it’ll keep capturing the traffic just like on a browser’s Network in Dev Tools
Now I deliberately added an erroneous code in my custom JS so that I could capture an exception in the monitor.
And if you look at the monitor, you’ll see that this has been captured.
And this is the wrong script I entered so that my code wouldn’t find the incorrect field name and throw an error when I try to retrieve value from an attribute that doesn’t exist (without null checking if the attribute exists or not)
However, best use case is when you ask end-users to join your session. Let’s see in the next session on how you can achieve this.

Invite Users to your Debug session

In the Model-driven apps monitor, here’s how you can invite other users to join your session –

In the Monitor, you’ll see Invite or Connect to a User. For this example, I’ll choose Connect user option.
Then, I can simply search for the User whom I want to generate a join link for.
Now, once this user is added, you’ll see a copy link option to copy the link and pass it on to the user who needs to join.
Once the end user has this link, then can join the session and they’ll see this message on their Dynamics model-driven app
And similarly, once they start reproducing the issue, you can start capturing the traffic on your end.

Hope this was useful! In order to fully understand the capabilities of Monitor for model-driven apps, here’s Microsoft’s official documentation – https://learn.microsoft.com/en-us/power-apps/maker/monitor-collaborative-debugging?WT.mc_id=DX-MVP-5003911

Hope this was useful!

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

Thank you!

Why Environment Variables don’t appear in Flows? | [Quick Tip]

March 5, 2024 priyeshwagh777 Power Automate Dataverse, Dynamics 365, environment variables, environment variables in flow, power apps, Power Automate, Power Platform

At times, if you are new to working with Environment Variables and you’re looking to use them in your Flows but don’t see them?

Here’s why!

Flows Outside Solutions

If you are creating Flows from the My Flows section, let’s see if you can access Environment Variables or not –

If you use My Flows way to create your Flows as shown below –
You won’t be able to access Environment Variables in that Flow

Flows in Solutions [Default and other Solutions]

So, you’ll need to have your Flows inside a Solution – even if you are creating a Flow in Default Solution, you’ll be able to access Environment Variables from another solution –

If you are in a Default Solution as shown below and you create a Flow there, you’ll be able to access Environment Variables.
And you create a Flow there, you’ll be able to access Environment Variables.

Hope this was useful!

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

Thank you!

Power Platform Pipelines | Blog Series

March 5, 2024March 5, 2024 priyeshwagh777 CRM with .NET Web Applications Dataverse, Dynamics 365, power apps, Power Automate, Power Platform

Here’s a blog series to get you up to speed on Power Platform Pipelines!

Setting up and Running Power Platform Pipelines

Here is what you need to get done in order to setup Power Platform Pipelines –

Advanced Settings

Scenario	Blog
Once request for deployment is submitted.	Pre-Export Step Required setting in Deployment Pipeline \| Power Platform Pipelines

Here’s official Microsoft Documentation on Power Platform Pipelines – https://learn.microsoft.com/en-us/power-platform/alm/pipelines?WT.mc_id=DX-MVP-5003911

Hope this was useful!

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

Thank you!

Run a Power Platform Pipeline

March 5, 2024 priyeshwagh777 Power Platform, Power Platform Admin Center Dataverse, Dynamics 365, power apps, Power Automate, Power Platform, Power Platform Admin Center, power platform pipelines

In case you setup your first Power Platform Pipeline and looking to test it out? This post is for you.

Or if you haven’t yet configured your Power Platform Pipelines first, refer this post – Setup Power Platform Pipelines

Now that you have your basic Power Platform Pipeline set in place, let’s run a created Pipeline!

Run Power Platform Pipeline

Here’s what you need to do in order to Run your pipeline –

Go to the Dev environment on which you have Hosted your pipeline (or which is supposed to be your first environment from where all the customization/configuration should move over).
Go to the Solution which you want to Run through the Pipeline.
For the simplicity of this example, this Solution has just 1 custom column on the Account table.
Now, click on Pipelines and look for the Deployed Pipeline which is ready to be used.
Now, once you get to see the stages which you have set in the blog post – Setup Power Platform Pipelines, those stages will appear here.
Then, verify the environment details mentioned and then click on Deploy here once you are sure.
Now, once you click on Deploy here, you’ll be given option to choose when you want to deploy – whether now or later.
For this example, I’m choosing Now instead of scheduling it for later. Then, I click Next and it’ll go into Validating Stage.
Once it all looks good, you’ll get AI generated notes already if you are in the US Region (at the time of writing this post). Then, click Deploy once everything looks good.
Once this is in progress in the background, you’ll see that the pipeline is deploying your solution.
Once this is completed, you’ll see that this is deployed successfully.
And this will be successfully deployed to the Target environment like so in the Managed Solutions section.

Hope this short tutorial was helpful!

Hope this was useful!

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

Thank you!

Enable Copilot for Dynamics 365 Sales environment

January 16, 2024 priyeshwagh777 CRM with .NET Web Applications copilot, Dataverse, Dynamics 365, dynamics 365 sales copilot, microsoft ai, microsoft copilot, open ai, power apps, Power Automate, Power Platform

Copilot for Dynamics 365 Sales is in Preview at the point of writing this post. Hence, I’ll start by showing how you can turn Copilot for Dynamics 365 Sales on for your environment.

It is recommended to do this in your Sandbox instances first.

Enable Copilot for Dynamics 365 Sales

Given that you have the correct licenses setup and you are a System Administrator, you can follow the below steps in order to enable Copilot for Dynamics 365 Sales –

Make sure you are in the Sales Hub app.
And then go to the App Settings
Here, you’ll see the Copilot as an option on the Sitemap, select that.
Note that all the Settings are turned off by default.
First thing you can do is, turn Auditing On. It’ll take a while to Save the changes in the background.
Then, you can turn on other features which are in Preview On and enable the Copilot App based on your Published apps in your environment.
Here are the Preview features which are listed under the See what’s in preview link in the above screenshot – https://learn.microsoft.com/en-gb/dynamics365/sales/view-copy-email-summary
Once the changes are saved, it’ll look like this in the Published state. the selections will remain the Publish button will be disabled.
At this stage, the Copilot has been enabled for the selected Apps in your environment.
Now, you can move to other options like Opportunities and Leads tabs on the settings page.
The Summary section in the entities will show which fields should be included in Summary information that Copilot will generate.
The Recent Changes in the entities will show which fields should be included to keep track of the changes which happen on these fields.

At this point, you are all set in configuring Copilot in your Dynamics 365 Sales environment. Next, I’ll write about how we can use the features which we enabled in this post and I’ll share link of the upcoming post here.

Hope this helps!

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

Thank you!

Hierarchy Settings in Dynamics 365 CE | Power Platform Admin Center

January 15, 2024January 15, 2024 priyeshwagh777 Power Platform Admin Center Dataverse, Dynamics 365, power apps, Power Automate, Power Platform

You must have seen Security Roles, Field Level Security, Access Teams etc. as a way to access records in Dynamics 365 CE (or CRM). Here’s what Hierarchy Security is all about –

There are 2 types of Hierarchy Settings in Dynamics 365 CE and what they mean in a short explanation –

Manager Hierarchy – Access control of records based on the Manager settings for a System User.
Position Hierarchy – Access control of records based on the Position of the System Users based on how they are placed in the Organization.

Configure Hierarchy Settings in Power Platform Admin Center

Given that you have Dynamics 365 Admin privileges, you can configure the Hierarchy Settings as below –

Go to the Environment’s Settings in Power Platform Admin Center
Now, you can expand and click on Hierarchy Settings
By default, these will be Disabled by default. Then, you can turn on the one which you want and configure the same.
In order to Configure the Manager Hierarchy Model, you can refer this post below –
Manager Hierarchy Settings in Dynamics 365 CE
In order to Configure the Position Hierarchy Model, you can refer this post below –
Position Hierarchy Settings in Dynamics 365 CE

Hope this was useful!

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

Thank you!

Position Hierarchy Settings in Dynamics 365 CE

January 15, 2024 priyeshwagh777 Power Platform Admin Center Dataverse, Dynamics 365, hierarchy settings in dynamics crm, position hierarchy, power apps, Power Automate, Power Platform, Power Platform Admin Center

In this post, you’ll learn how to configure Position Hierarchy for Dynamics 365 CE environment –

Let’s first look at the scenario which we want to look at and then how we can configure the Hierarchy to limit and show the Positions of the Users the intended data.

Scenario

Let’s consider the below scenario on who report to whom in the org CFT300 based on the below Positions in the Org –

In the above example,

Salesperson should see then own records.
VP of Sales should say their own records and of Salesperson roles too.
Executive Director should see their own records and only those of VP of Sales, but not Salesperson roles.

Position Hierarchy

Given that you already know how to navigate to Hierarchy Settings in Power Platform Admin Center, refer the below to understand how to configure the same based on the above scenario –

Once you are in the Hierarchy Settings in the Environment’s Settings area in Power Platform Admin Center –
Now, you can select Enable Position hierarchy Model and click on Save to apply the Position Hierarchy Model access to your environment. Once Saved, you’ll see as below.
The Depth defines how many levels of Positions should a User be able to access records of other user in other positions in a top-down approach.
Let’s click on Configure in order to start setting up the Positions in the Org.
Now, based on the diagram above, I’ll create the Position hierarchy on this page
Now, based on the same, I’ve created the below Positions in a hierarchy

And the tree looks like this –
Now, next is to assign these Positions to different Users in Power Platform Admin Center. If you go to Users and select any of the Users, you’ll see Change Position button on the ribbon.
Then, you can find the Position you created which you want to give to the Users. Select it and Save it on the Pane.
Complete the process for all the Users who need to be having one of the Positions you created.

So based on this, Jack Green will be the Executive Director and will be able to access Amit Prajapati’s records and not Vidit Gholam’s or Ethan Rebello’s records.

Also, the selected Tables are the ones to which the Position Hierarchy should apply.

Now, based on the above setup and the Scenario provided, let’s look at how the records will be visible to the Users in the hierarchy.

Dynamics CRM Records access based on the Position Hierarchy Security –

Let’s start reviewing from the bottom of the hierarchy. Vidit and Ethan, both will see their own record in the Active Accounts view and no one else’s based on the Hierarchy Settings.
Also, note that the Read privilege for all the Users in their Security Roles is set to “Users” and not “Organization“.

Ethan Rebello –

Vidit Gholam –
We move 1 level up to Amit Prajapati – he’ll see his own record and also Vidit’s and Ethan’s records in Active Accounts view.
And Jack Green can access his own record and as he’s the Executive Director and can see VP of Sales position records, he’ll see only Amit’s records for Accounts and not Ethan’s and Vidit’s.

This will change if we increase the Depth to 2, 3 and onward based on the hierarchy structure.

Hope this was useful!

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

Thank you!

Manager Hierarchy Settings in Dynamics 365 CE

January 15, 2024 priyeshwagh777 Power Platform Admin Center Dataverse, Dynamics 365, hierarchy settings, manager hierarchy in dynamics crm, power apps, Power Automate, Power Platform, Power Platform Admin Center

In this post, you’ll learn how to configure Manager Hierarchy for Dynamics 365 CE environment –

Let’s first look at the scenario which we want to look at and then how we can configure the Hierarchy to limit and show the Managers the intended data.

Scenario

Let’s consider the below scenario on who reports to whom in the Org CFT300 used in this example –

In the above example,

Manager of Vidit Gholam and Ethan Rebello is set as Amit Prajapati.
Manager of Amit Prajapati is Jack Green.

And this structure looks as below in Dynamics 365 CRM environment –

Note: Please note that in order to set Hierarchy Settings correctly, the Read privileges on the intended entity must be set to “User” level. If it is set to “Organization”, the the User will anyway be able to access everyone’s records despite Hierarchy Security Settings in place.

Manager Hierarchy

Given that you already know how to navigate to Hierarchy settings in Power Platform Admin Center, refer the below to understand how to configure the same based on the above scenario –

Once you are in the Hierarchy Settings in the Environment’s Settings area in Power Platform Admin Center –
Now, you can select Enable Manager hierarchy Model and click on Save to apply the Hierarchy Model access to your environment.
The Depth defines how many levels should a Manager be able to access records of the Users in the top-down approach.
You’ll also need to set the Users’ Manager in Power Platform Admin Center. If you go to the Users and select any 1 of them, you’ll see Change Manager button on the ribbon.
And, search the User who should be the Manager of the User which you are editing.

So based on this, Jack Green will only be able to access Amit Prajapati’s records and not Vidit Gholam’s or Ethan Rebello’s records.

Also, the selected Tables are the one to which the Hierarchy Security should apply.

Now, based on the above setup and the Scenario provided, let’s look at how the records will be visible to the users in the hierarchy.

Dynamics CRM Records access based on Manager Hierarchy Security –

Let’s start reviewing from the bottom of the hierarchy. Vidit and Ethan, both will see their own record in the Active Accounts view and no one else’s based on the Hierarchy Settings.
Also, note that the Read privilege for all the Users in their Security Roles is set to “User” and not “Organization” level.

Ethan Rebello –

Vidit Gholam –
We move 1 level up to Amit Prajapati – he’ll see his own record and also Vidit’s and Ethan’s records in Active Accounts view.
And Jack Green can access his own record and as he’s the Manager of Amit Prajapati, he’ll only see Amit’s records for Account and not Ethan’s and Vidit’s.

This will change is we increase the depth to 2, 3 and onward based on the hierarchy structure.

Hope this was useful!

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

Thank you!

Time and Materials Billing Backlog table in Project Operations

January 8, 2024 priyeshwagh777 Project Operations Dataverse, Dynamics 365, dynamics 365 project operations, power apps, Power Automate, Power Platform, time and materials billing backlog, time and materials project operations

Even wondered what is Time and Materials Billing Backlog table in Project Operations which you see in the Sitemap but you might not be sure what records are in it –

Time and Materials Billing Backlog

Here’s the purpose of Time and Materials Billing Backlog entity –

Given that you have 2 Time Entries Submitted for Approval to the Project Management / Account Manager.
When the Time Entries are Submitted, the Approver receives them for Approval. The Project Approver can then Approve the Time Entries.
Once they Approve the Time Entries, they are turned into Actuals (msdyn_actual) in Project Operations.
Then, Actuals are then Supposed to be marked as Ready to Invoice.
So, when the Actuals are the created and even when they are marked Ready to Invoice, that’s when they appear in Time and Materials Billing Backlog view.
This table is in fact Actuals table itself! 😊 (There’s no Time and Entry Billing Backlog as a separate Table in Dataverse).
In fact, Accounting managers or Project Managers can Ready the Actuals from the Time and Materials Billing Backlog table itself.
Now, then the Invoice is created for the ready Actuals, they are added to Invoice Lines
And then, they are removed from the Time and Materials Billing Backlog view.

Hope this was useful!

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

Thank you!

Enable OneNote Integration for Dynamics 365 Sales environment

January 2, 2024 priyeshwagh777 d365 for sales, Dynamics 365 CE Dataverse, Dynamics 365, onenote integration, onenote integration with crm, power apps, Power Automate, Power Platform, sharepoint integration

Since collaboration tools like Teams, SharePoints are a norm, so is OneNote. Here’s how you can enable OneNote Integration in your Dynamics 365 CRM Instance –

Settings

Given that you are a Dynamics 365 Administrator, you can navigate to Power Platform Admin Center of your environment –

Go to the Settings on the Environment you want to enable OneNote Integration on
Once you are in Settings, you can expand Integration section and then click on Document management settings.
Then, you’ll be redirected to the classic UI and there, you can select Enable OneNote Integration (provided that SharePoint Based Document Integration is already enabled).
It’ll open up this dialog box and you’ll see the pre-enabled OneNote for the tables which you want to enable. You can choose the ones you want to enable OneNote Integration for and click Submit. This dialog box will then close.
Also, double-check on the entity level if OneNote Integration is turned On or not.
Once this is done, you can refresh the record on which the OneNote Integration is enabled and click on + on the Timeline to show the Activity options. You’ll see OneNote appear as well.
Once you click on it, it’ll be redirected to SharePoint location where the OneNote notebook is created.
Now, when you come back on the record and click on Related section and go to Documents. You’ll see the OneNote notebook appear there in the record.

Hope this post helps!

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

Thank you!

D365 Demystified

A closer look at Microsoft Dynamics 365.

Dynamics 365

Use Monitor to debug Model-driven apps remotely | Power Platform

Capture events from Monitor in Model Driven Apps

Invite Users to your Debug session

Like this:

Why Environment Variables don’t appear in Flows? | [Quick Tip]

Flows Outside Solutions

Flows in Solutions [Default and other Solutions]

Like this:

Power Platform Pipelines | Blog Series

Setting up and Running Power Platform Pipelines

Advanced Settings

Like this:

Run a Power Platform Pipeline

Run Power Platform Pipeline

Like this:

Enable Copilot for Dynamics 365 Sales environment

Enable Copilot for Dynamics 365 Sales

Like this:

Hierarchy Settings in Dynamics 365 CE | Power Platform Admin Center

Configure Hierarchy Settings in Power Platform Admin Center

Like this:

Position Hierarchy Settings in Dynamics 365 CE

Scenario

Position Hierarchy

Dynamics CRM Records access based on the Position Hierarchy Security –

Like this:

Manager Hierarchy Settings in Dynamics 365 CE

Scenario

Manager Hierarchy

Dynamics CRM Records access based on Manager Hierarchy Security –

Like this:

Time and Materials Billing Backlog table in Project Operations

Time and Materials Billing Backlog

Like this:

Enable OneNote Integration for Dynamics 365 Sales environment

Settings

Like this:

Capture events from Monitor in Model Driven Apps

Invite Users to your Debug session

Share this:

Like this:

Flows Outside Solutions

Flows in Solutions [Default and other Solutions]

Share this:

Like this:

Setting up and Running Power Platform Pipelines

Advanced Settings

Share this:

Like this:

Run Power Platform Pipeline

Share this:

Like this:

Enable Copilot for Dynamics 365 Sales

Share this:

Like this:

Configure Hierarchy Settings in Power Platform Admin Center

Share this:

Like this:

Scenario

Position Hierarchy

Dynamics CRM Records access based on the Position Hierarchy Security –

Share this:

Like this:

Scenario

Manager Hierarchy

Dynamics CRM Records access based on Manager Hierarchy Security –

Share this:

Like this:

Time and Materials Billing Backlog

Share this:

Like this:

Settings

Share this:

Like this: