Microsoft Dynamics 365/CRM entities often have some special statuses that would prohibit update of the entity record when there are any other fields involved but the record itself is in a certain status. One of such entities is the CRM case entity which has a physical name of incident in the system. If a case is resolved, you can't make any further updates to the record, otherwise you will receive an error indicating the case has been resolved, it needs to be reopened in order to make changes. This applies to other entities that might have similar restrictions, and it imposes a challenges to data integration (or ETL) development. In this blog post, I will show you how to work around this situation.

As a professional Dynamics 365/CRM developer, you want your code to be as efficient as possible. I have often run into a code structure that first checks the existence of a particular field value in CRM entity property bag, and then trying to access the value using a dictionary lookup. This is very inefficient. In this blog post, I will show you why and how you can address the situation.

Microsoft Dynamics 365/CRM uses some close entities to capture the reason why the primary record was closed with some additional information. In this blog post I discuss how to migrate CRM close or resolution entities in your ETL process properly to avoid creating duplicates for those entities in your target system.

Microsoft has retired the support of ACS. This blog post discusses what this means to you as a Dynamics 365/CRM developer, and what action should be taken moving forward.

At KingswaySoft, we always try to embrace new platform features as much and as soon as we can. However, in our support effort in helping one of our clients, we ran into a very strange situation that when we try to make an update of a CRM record's statecode/statuscode fields, it will always create two audit records for one service call. In this blog post, I will show you the symptom of the problem and how you can fix it.

There are often times when you need to perform a cascaded lookup in your CRM SSIS/ETL project for cases such as when a lookup field could be located in 1 of 2 fields. This blog post will show you how you can perform such cascade lookups

There are many reasons that you might want to extract attachments from Microsoft Dynamics 365/CRM. For CRM online users one of the most appealing reason might be uploading the CRM attachments to a cloud storage such as SharePoint or OneDrive as a more cost-effective storage option. In this blog post, I will show you how to extract CRM attachments and save them to your local file system.