Microsoft Dynamics 365 – Page 168 – Nishant Rana's Weblog

Fixed – You don’t have permission to access any of the organizations in the Microsoft Dynamics CRM Online region that you specified error in USD Client Application

Recently after upgrade to version 9.1 and USD 4.0, some of the users started getting the below error while trying to login into the USD Client Application.

You don’t have permission to access any of the organizations in the Microsoft Dynamics CRM Online region that you specified. If you’re not sure which region your organization resides in, choose “Don’t know” for the CRM region and try again. Otherwise check with your CRM administrator.

They were able to login to Dynamics 365 CE through browser though.

Eventually turned out that few of the sites (url(s)) were getting blocked because of the network policy on the agent’s machine. Allowing those sites resolved the issue.

Hope it helps..

Case: Merged vs. Child Cases

Jeevarajan Kumar

We will go back to the basics and see one of the basic features of case entity which is confusing at times to the beginners, Merged Case vs. Child Case. What are they? Why and when to use them?

Merge Case:

What is Merged Case?

When a case is merged, the state of the case is changed to cancelled, and the status is changed to merged. All of the open case activities, emails, and attachments that a case has are now associated with the case it is merged into.
When you merge a case that has child cases, those child cases become child cases of the new parent case they get merged into.

How?

The unselected cases will be marked as canceled and will be mapped under the selected case.

Merged Case

Why and When?

There are scenarios where a customer opens multiple cases about the same issue through different support channels…

View original post 237 more words

CrmRecordId and IsNew Output in CRM/CDS Destination Component

In CRM/CDS Destination Component of SSIS Integration toolkit we can found 2 output column as part of error handling

In case of Create

CrmRecordId will have the GUID of the newly created record, which could be used for any further processing
IsNew will list whether this is a new record or not.

Our package: –

Suppose we have the following record in our source (here ID is the alternate key column used for Upsert)

If all the records are new and are created we will get the following output.

Now if we delete the Test User 2 and Test User 3 record and run the package again, which should now create 2 records and update one record i.e. Test User 1 during Upsert.

The output would be as below

It will return the GUID of the record irrespective of Update or Create and IsNew will specify whether the record is newly created or updated.

Hope it helps..

[D365 CE Online] Debug Async Plug-in using “Persist to Entity” profiler option

Rajeev Pentyala – Technical Blog on Power Platform, Azure and AI

As you are aware, using Plug-in Profiler option we can debug D365 online plug-ins by throwing exception and capturing the Serilaized profile. Refer my previous article

With the ‘Exception’ profiling option, you first need to trigger the event and capture the exception log. For example, if you need to debug “Post Account Create” plug-in, you first need to trigger the event (i.e., Create Account from D365 application) and capture the exception log. This ‘Exception’ option would be apt, if your plug-in registered in Sync mode.

What if your plug-in is Async? Answer is, using “Persist to Entity” profiler option.

Let’s see how to debug Async Plug-in step by step.

Configuring Profiler in Plugin Registration Tool:

Connect to your Dynamics instance using Plug-in registration tool.
Click on ‘Install Profiler’ button
Register a new plug-in assembly and add an Async step
- In this article, I registered an Async step on Post…

View original post 197 more words

Unexpected error (SQL Timeout error) while trying to delete Audit Log

We had around 200 GB of Audit Log data in our Production Environment (Online), but while trying to delete it through Audit Log Management resulted into unexpected error.

The only option is to raise the support ticket with Microsoft. We also raised the same but it unfortunately resulted in our Production Server being down for brief period of time because of time out issue while performing the operation in Audit Base.

So, in short if we are facing issue while deleting log ourselves, we need to raise the support ticket and also the plan the same during downtime or weekends when users are not using the system.

Hope it helps..

How To Access Master & Duplicate Record In Merge Operation Plugin

Passion Dynamics

Here is a quick blog on how to access master & child records during a Merge operation in a plugin.

I recently had to develop a plugin where in I needed to do some manipulation with the records being merged.

You can access three entities in your plugin when a record is merged from Context.InputParameter :

1. SubordinateId – the duplicate record
2. Target – the master record
3. UpdateContent – a temp entity contains the final attribute as outcome of the merge operation.

To Access them in the code simply do this:

Entity duplicate = context.InputParameters[“SubordinateId“]; // To access the duplicate record simply retrieve the attributes using service.retrieve and by proving the duplicate.Id.

EntityReference target= (EntityReference)context.InputParameters[“Target“];

Entity finalRecord = context.InputParameters[“UpdateContent“]; //To access the final record simply retrieve the attributes using service.retrieve and…

View original post 10 more words