Today, we are pleased to announce the availability of SSIS Integration Toolkit for Microsoft Dynamics CRM v1.1 SR4 (Service Release 4). This release includes some important updates and bug fixes, as listed below.
- Update: CRM Source Component now supports reading from partylist fields when SOAP 2007 service endpoint is used. (If your CRM source component was created with a prior version with partylist fields included, in order for them to work, you will have to re-create the source component in order to populate CRM metadata properly. You only need to do so if SOAP 2007 service endpoint is used.)
- Fixed: When connecting to CRM IFD environment using SOAP 2007 service endpoint, you receive an error "Sever was unable to process request (System.Web.Service)" although you have provided correct login credentials. (Thanks to Richard for reporting this issue)
- Fixed: When writing data to a N:N relationship entity if SOAP 2011 service endpoint is used, you get the following error message: "CRM server returned an error: Input field type 'String' does not match expected type 'Relationship' for field 'Relationship' (Error Code: -2147220715, Detail Message: Input field type 'String' does not match expected type 'Relationship' for field 'Relationship')"" (Thanks to Adrian for reporting this issue)
- Fixed: In CRM destination component, if Upsert is used as action while Primary Key is selected as the Upsert Matching Criteria option, when the primary key value from the upstream component is of a NULL value, the destination component will report "Error: CRM field was not found: xxxxx", where xxxxx is the primary key field name. (Thanks to Scott for reporting this issue)
Again, in order for partylist fields to work to CRM source component when SOAP 2007 service endpoint is used, you will have to re-create the source component in order to populate CRM metadata properly.
The new release is now available for download at our product download page. In order to install the new build, you will need to uninstall the previous installation first.
Thanks for reading.