Advanced Topics

For some advanced integration topics that are not covered in this manual page, you should check out our online FAQ page which covers some specific integration scenarios, including:

  • Frequently asked licensing questions
  • Best practices and performance tuning
  • How to work with CRM partylist fields
  • Some frequently encountered errors
  • and more...

Known Limitations

The following are some limitations of the software which are either by-design or due to the constraints of Microsoft Dynamics 365/CRM or SSIS platform:

  • In the CDS/CRM Source Component, with the FetchXML option, if you are using linked entities in your FetchXML queries, the CRM component returns NULL values for the fields from linked entities. To avoid this, provide an alias for each linked entity.
  • When reading from virtual fields, like lookup name fields or OptionSet name fields, make sure to also include the base field (ex. the lookup field or OptionSet field) in the CRM Source Component, otherwise there will be no values returned for those name fields.
  • The Destination Component will not report the CrmRecordId (guid) or IsNew Columns for N:N relationships.
  • When using a version prior to our v10.2 release to upsert records into Dynamics 365 CE/CRM system with a Batch Size (greater than 1) specified in the destination component, you might end up with duplicate records created in the system when there are duplicates from the source system. To avoid such problems, you should consider upgrading your software installation to v10.2 or later, as we started to take care of this particular situation by eliminating duplicates before writing to the target system starting from our v10.2 release. Even better, in our v11.1 release, we introduced a new option called Optimization on Source Duplicates which you can use to specify how duplicate records are handled before writing to the target system - with one of them being to remove the duplicates before writing. If, by any chance, you can't upgrade the software installation to v10.2 or later, you would have to either set the destination component's Batch Size and Concurrent Thread Number both to 1, or otherwise, you will have to eliminate duplicates from the source in the same batch before sending them in to the CDS/CRM Destination Component.
  • Our software does not support multi-factor authentication (MFA), as our software is primarily designed for non-interactive use, and multi-factor authentication usually involves human intervention, which is not possible for unattended SSIS job processes.
  • When writing to CDS/CRM that involves impersonation such as writing to the createdby or modifiedby fields using the CRM or CDS destination component, the provided user has to be an active user in the application with proper privileges. Otherwise if the provided user is disabled in the system, or if it is a stub user without a license, the provided input value will automatically be replaced by the connection user instead.