In Dynamics 365 CE/CRM, Actions are a type of process that can be invoked to perform a specific task. They supports input parameters that can be passed in as arguments if required, as well as Output parameters to obtain a status or any parsed value. In our KingswaySoft Dynamics CRM Destination component, you can easily trigger an Action by using the ExecuteWorkflow option and configure the output parameters as well. In this blog post, we will go through the steps to accomplish this.

When writing to Dynamics 365 CE/CRM entities, it is important to remember that when dealing with Option values or Choice type fields, these are a set of defined values applicable for a field within the scope of the Dynamics 365 CRM instance. Your source component may have a different value set for the same field, which is common when the Source is not a Dynamics 365 CRM instance. In this blog post, we will show you how to use KingswaySoft's Option Value Mapping feature to translate and handle such fields easily.

Moving emails across Dataverse or Dynamics 365 environments, especially handling email attachment records, poses unique challenges due to the specific behaviors of the Dataverse/CRM email attachment entity. In this blog post, we will demonstrate how to work with the ActivityMimeAttachment entity in Microsoft Dynamics CRM for accurate data migration, using the CDS/CRM Destination components available in our Dynamics 365 Toolkit.

OAuth offers clear advantages over basic authentication, establishing it as the superior choice for data integration projects that involve processing or consuming your Dynamics 365 Business Central data. In this blog post, we will explore the secure and flexible nature of OAuth, its advantages over basic authentication, and its role in data integration projects. By following the steps outlined in this concise guideline, you will be able to create a connection manager using OAuth authentication for integration with Dynamics 365 Business Central online.

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.