While migrating from CRM to CRM, or any other Source system to CRM, in an ETL, records will need to be associated with users. And since the Source and Target Systems are different, there may not be a guarantee that some users may still exist in the organization. And in such cases, such users become either unlicensed, or stub users. These type of users have restrictions when it comes to being set as an owner of records, and in this blog post, we will see how this can be handled efficiently.

It is not unusual to run into a business requirement that you need to extract Dynamics 365 metadata during your ETL process. We used to believe that this is not a general requirement until we have recently announced our DES deprecation replacement solution, in which it is important to have a way to retrieve the list of Option Set values along with their label values in the system since Dynamics Entity Changes feature only returns integer values for those option set/picklist options. In this blog post, we will discuss this scenario and how to work with our DES deprecation replacement solution.

When working with Dynamics 365 online, your integration performance is subject to what is allowed by the server infrastructure managed by Microsoft. In particular, Microsoft has a throttling strategy in place to prevent exhaustive resource usage on the server-side from each individual tenant. This is for the good reason of making sure that the servers operate in a healthy environment, so that it does not degrade the overall performance of all other tenants in the same server group, while one tenant is performing a high-paced data load. However, this can create challenges when your data load has to be completed in a particular time window, in which case you might have exhausted all of your options to speed up the data load performance. In this blog post, we will discuss a new feature that can be used to overcome this limitation and boost data load speed.

In this blog, we are trying to get the metadata information from Dynamics 365 CRM API and save the entities and attributes in different tables. This is useful in many use cases where you wish to get a list of all the entities that are present, and its corresponding metadata as a part of your integration - Especially for further parameterization plans.

Our Dynamics 365 toolkit offers an in-place lookup feature that provides many unique capabilities in supporting various lookup requirements. While the feature is extremely flexible and easy to use, there are certain limitations, such as it cannot be used in a transformation component, and it can support up to 2 different fields you can look up against for reach lookup configuration. In this blog post, we will demonstrate how you can use our recently released Premium Service Lookup component to perform some more advanced lookup scenarios when working with Dynamics 365 CDS/CRM/CE/Dataverse connections.

Many of our clients are switching their Authentication to OAuth for their connections in our CDS and Microsoft Dynamics 365 CRM components. OAuth provides a better security infrastructure to protect your Dynamics data. The process of switching to OAuth authentication can be a bit confusing in the beginning if you have never worked on the concept before. In this post, we will walk you through the process with some great details to help you understand what is required and how OAuth works for our CDS/CRM connections.

Our CRM migration starter pack has been widely used by many clients worldwide. We have just made some further enhancements to cover some important migration tasks.

Learn how to quickly delete numerous records in Microsoft Dynamics 365 CRM at once with the BulkDelete action.