Today we are pleased to announce the release of SSIS Integration Toolkit v3.2 for Microsoft Dynamics CRM.
The new release includes the following enhancements and bug fixes.
- New: We added a configurable option called Enable Stack Trace, once enabled, it will report any exception encountered with stack trace included
- New: When switching Source Type from Entity to FetchXML, CRM source component will automatically generate a FetchXML query based on the fields that have been selected in Entity mode (Thanks to Chris for the suggestion)
- New: We added support of HTTP compression (Thanks to Angel for the assistance in validating this feature)
- Change: CRM Source component now respects the count (page count) and page (page number) attributes that you have specified in FetchXML query
- Fixed: When reading data from CRM memo fields (such as account's description field), you might run into an error "The value is too large to fit in the column data area of the buffer" (Thanks to Mel for reporting this issue)
- Fixed: When using CRM components in a Foreach Loop container, CRM connection manager is always connecting to the same CRM server even though its ConnectionString has been changed (Thanks to Mel for reporting this issue)
- Fixed: CRM OptionSet Mapping Component doesn't work properly for SSIS 2012 (Thanks to Phillip and Joost for reporting this issue)
- Fixed: You might run into an error "System.ArgumentNullException: Value cannot be null. Parameter name: key" with CRM OptionSet Mapping component
- Fixed: When writing data to userquery entity, you might encounter an error "Attribute 'returnedtypecode' cannot be NULL" (Thanks to John for reporting this issue)
- Fixed: You might run into an error "System.ArgumentException: Value does not fall within the expected range" when writing to CRM (Thanks to John for reporting this issue)
- Fixed: When executing a script component using CRM connection manager, you might run into a serialization error (Thanks to Urs for reporting this issue)
With the new release, we made some performance improvement, particularly if you are using SQL Server 2008 R2 or earlier, you should be able to see a 300-600% performance improvement when reading data from CRM Online.
Please be advised that the FetchXML related change might affect your CRM Source component's performance if you previously had count (page count) specified in your FetchXML query, since the new version will use the count (page count) to overwrite the component's Batch Size setting. You might want to revisit your FetchXML query before upgrading to the new version, particularly if you have used Stunnware Tools to build your FetchXML queries, which always have a default count of 50 in the query.
Hope you find the new release useful, thank you for your continued support, as always.