Dynamics 365 – Page 58 – Nishant Rana's Weblog

Fixe – Error – Access to the resource is forbidden while trying to connect to Azure Data Lake Storage Gen2 using Power BI Desktop

While trying to connect to Azure Data Lake Storage Gen2 through Power BI Desktop we got the below error

Came as surprise cause the user was had the owner role assigned to the container

It turned out we need to assign the Storage Blob Data Reader role to the user.

After assigning the role we were able to connect successfully.

Posts on Azure Data Lake

Hope it helps..

How to – Use Azure Synapse Link – Export data from Common Data Service to Azure Data Lake Storage Gen2

Azure Data lake store gen 2 can be described as a large repository of data, structured or unstructured built on top of Azure Blob storage, that is secure (encryption – data at rest), manageable, scalable, cost-effective, easy to integrate with.

Also check out – setup Azure Synapse with Dataverse – https://nishantrana.me/2021/06/16/how-to-setup-azure-synapse-link-microsoft-dataverse/

Export to Data Lake allows for continuous replication of CDS entities to Data Lake Storage Gen2, which involves initial write followed by incremental writes, which can be consumed by Power BI, Azure Data Factory, Azure Data Bricks, and Azure Machine Learning.
Replication of standard and custom entities having change tracking enabled and create, update, and delete operations.
Any changes in data and metadata are pushed automatically without the need of setting any refresh intervals.

Let us first create a general-purpose V2 storage account to access all of the Azure storage services like blobs, files, etc.

The storage account must be in the same Azure AD tenant.

https://portal.azure.com/

Search for Storage Accounts.

Here we have used a trial to create the storage account.

Leave the Account kind, Replication, and Blog Access as the default values while creating the storage account.

Before selecting Review + Create, navigate to the Advanced tab and enable the Hierarchical Namespace.

After validation is done and is successful, click on Create to create the storage account.

With the storage account created successfully, navigate to PowerApps select the option Export to data lake.

Select New link to data lake

Specify the storage account created earlier.

Select the entities to be exported to the data lake. Enable change tracking for the entities, as only these entities will be exported.

Clicking on save will link the CDS environment with Azure data lake storage.

It will create the file system in the Azure storage account having a folder for each entity selected.

and will start the initial sync.

we can use the Manage entities option for adding or removing the linked entities.

Inside Azure Portal, we can navigate to the storage account and select the Storage Explorer.

Expand commondataservice-environmentName-org-Id
container to view the details.

The CSV file will contain the data

Here Model.json is the metadata file in the CDM folder

that describes the data in the folders, metadata, and location.

More details-

https://www.bluegranite.com/blog/10-things-to-know-about-azure-data-lake-storage-gen2

Posts on Azure Data Lake

Hope it helps.

Use Monitor to troubleshoot forms in the model-driven app (preview)– Dynamics 365

The new monitor feature added for the Model-driven apps can be used for troubleshooting issues with form related events.

We have 2 ways to access the monitor option.

Select the Model-driven app inside Power Apps and select Monitor in the command bar.

The other option is to add the parameter &monitor=true to the end of the URL

And select the monitor option

This will open the monitoring session in a new tab.

Click on the Play model-driven app.

This opens the app connected to the monitor session.

We can see any action performed tracked.

We can filter Category column to check specific events related to form.

Select the row to get the details populated on the right side.

Get all the details below

https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/monitor-form-checker

Hope it helps..

Email experience now available in Dynamics 365 Mobile App – 2020 Release Wave 2

With 2020 Release Wave 2, users can now finally compose, edit, and send emails from the Dynamics 365 Mobile App.

Check other blog posts on Release 2020 Wave 2

Now mobile users can –

Compose and send email from Dynamics 365 Mobile app

Navigate to Activities menu from the home page.

We can see the Email entity added there.

Clicking on it allows us to compose an email from within the app.

We have the full email editor formatting available.

We also have the functionality of inserting template, signature, knowledge article, etc. available.

We can also create email records from within the Timeline section.

Check the other blog posts on Dynamics 365 Mobile App

Hope it helps..

ARC and SLA Migration tool (Preview) in Dynamics 365 – 2020 Release Wave 2

With 2020 Release Wave 1, new experience was added for administrators which uses Power Automate for defining rules, conditions, and actions for SLA and Automatic create and update records rule.

https://nishantrana.me/2020/02/26/automatic-record-creation-and-update-rules-enhancements-in-dynamics-365-customer-service-2020-release-wave-1/

Now 2020 Release Wave 2 provides a tool to migrate the existing rules and SLA from classic app to the Customer Service Hub that uses Power Automate.

Other blog posts on 2020 Release Wave 2

Say e.g. we have below rule created for Task in the classic or legacy experience.

For the rule item, for simplicity, we have kept the condition as a description field containing data.

Now let us open the Customer Service Hub, and navigate to Service Management Area – ARC and SLA Migration tool

There we can see the 1 rule that we had created listed.

Let us click on the Start Migration button to start the migration.

Let us select the category and click on Next.

The next step is pre-migration check

It shows as passed after the check

The Rules and items to migrate give the option to select the rules to migrate.

The next screen gives the option to review the selection before starting the migration.

Clicking on Start migration starts the process.

Below we can see the migration completed.

Once completed, we are presented with the below summary screen

The new rule has the suffix migrated added to its name.

We can open the rule to check its definition. (and activate it)

As expected we have our rule updated to use the Power Automate.

Below is the rule created in legacy experience.

Note: –

Earlier we got the below error message, which was quickly resolved by Microsoft after it was reported to them.

message=’msdyn_migrationtracker’ entity doesn’t contain attribute with Name = ‘correlationid’ and NameMapping = ‘Logical’. MetadataCacheDetails: ProviderType=Dynamic, StandardCache=True, IsLoadedInStagedContext = False, Timestamp=3625460, MinActiveRowVersion=3625460, MetadataInstanceId=37958858