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 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.
  • The Destination Component will not report the CrmRecordId (guid) or IsNew Columns for N:N relationships.
  • When creating records using the Upsert action and a Batch Size of greater than 1, there may be a case where duplicate records are created in CRM - if there are duplicate records within the same batch. There are two ways this issue can be handled:
    1. Set the Batch Size to 1.
    2. Eliminate duplicates from the source in the same batch before passing in to the 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.