Incremental Load in SSIS with Diff Detector
Easily develop incremental load in SSIS within one data flow by utilizing SSIS Productivity Pack. In this blog post we will cover how you can use Diff Detector and Premium ADO.NET Source & Destination to quickly create performant incremental loads in SSIS.
Incremental Load in SSIS Made Easy
In this blog post we will cover how you can use SSIS Productivity Pack to quickly develop SSIS incremental load packages within one data flow without needing to perform any lookups.
Integration between Magento and Microsoft Dynamics 365/NAV
In this blog post we will discuss how you can integrate your commerce platform (Magento) with your ERP (Microsoft Dynamics 365/NAV) to provide seamless data transfers between the two systems.
How to Retrieve Incremental Changes from CRM in your ETL Process
In this blog post we discuss how you can take advantage of CRM Change Tracking within your data synchronization project to only sync records that have changed.
Access CRM Fields in an Efficient Way
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.
Migrate CRM close or resolution entity records in your ETL process
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.
Dance with CRM Statuses In ETL Project
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.
ACS Deprecation - What does this mean to you as a 365/CRM developer
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.