Version 9.1 - October 6, 2017

The following are the updates and enhancements made for each group of components. 

  • [All] New: We added a new documentation generation button to all SSIS components that can be used to generate a Word document which describes the component's metadata including relevant mapping, and so on.
  • [AX] New: We added a "Data Scope" option in AX connection manager, which can be used to enable cross-company support for Dynamics 365/Operations.
  • [AX] New: We added a "Client Secret" option in AX Connection Manager, which can be used to authenticate using Azure Web application.
  • [AX] New: We added a "Send datetime values in UTC Format" option to the AX destination component.
  • [CRM] New: We added an "impersonateas" option in the Destination CRM Field for userquery & userform entity when Delete action is used in the CRM destination component.
  • [CRM] New: We added support of a new action - Bulk Delete to the CRM destination component, which brings the number of write actions available to a total of 9.
  • [CRM] New: We added a new output column "NoChangesRequired" in the CRM destination component's Default Output, which returns true when there is no changes detected in the incoming record when compared to what's in CRM.
  • [CRM] New: The CRM OptionSet mapping component now supports a Locale ID input to be used when creating new option values. In the case that the option's internal integration value already exists in the target CRM system, the provided label will be updated or created based on the Locale ID provided.
  • [NAV] New: We added support for multi-threaded writing in the NAV destination component, you can now use one single option to configure the number of simultaneous threads used to write to Dynamics 365/NAV in parallel.
  • [AX] Enhancement: Connections to Dynamics 365 for Operations are now made with the latest and greatest TLS protocol whenever possible.
  • [CRM] Enhancement: We add a number of additional fields that can be written to those close entities when working with incident, opportunity, quote, and salesorder entities.
  • [NAV] Enhancement: Enhanced error handling.
  • [NAV] Enhancement: Connections to Dynamics 365 for Financials are now made with the latest and greatest TLS protocol whenever possible.
  • [AX] Fixed: You may get "Invalid HTTP Request" error when using Update or Upsert action in AX Destination component.
  • [CRM] Fixed: When there is an optionset/picklist field in the CRM destination component that is not mapped to any input, but it happens to have been removed from the CRM system, the destination component will complain about not being able to get metadata for the optionset/picklist field.
  • [All] Update: Some updates to the licensing component.

Version 9.0 - July 7, 2017

The following are the updates and enhancements made for each group of components.

  • New: We added support for SQL Server 2017.
  • [AX] New: We added support for Dynamics 365/Operations.
  • [CRM] New: We added support for multi-threaded writing in the CRM destination component, you can now use one single option to configure the number of simultaneous threads used to write to CRM in parallel.
  • [CRM] New: We added support of Delete action for "audit" entity.
  • [CRM] New: We added a new "Send" action to the CRM destination component which can be used to send CRM emails.
  • [CRM] New: We added Max Rows Returned option in CRM source component, which can be used to limit the number of records returned.
  • [CRM] Fixed: For some CRM entities, the Create action in CRM destination component might post two service calls instead of one when the provided statecode is the default one.
  • [CRM] Fixed: CRM destination component tries to retrieve OptionSet/Picklist field metadata even the field is not mapped to an input column.
  • Enhancement: Improved high-DPI support.
  • Enhancement: Some minor GUI improvements.
  • Enhancement: We added command line support for License Manager program.
  • Update: We no longer deploy Newtonsoft.Json.dll assembly to Windows GAC.
  • Update: All our assemblies and installation .msi files are now signed.
  • Fixed: If you have an Ultimate trial license, it may still report as not licensed.

Version 8.1 - March 15, 2017

The following are the updates and enhancements made for each group of components.
  • Microsoft Dynamics 365/CRM Components
    • New: We added the new German CRM online region for selection in CRM connection manager.
    • Fixed: CRM source component returns empty values for custom customer name field, even though the field may have a value.
    • Fixed: CRM OptionSet mapping component may report an error in its UI if any mapped option values have recently been deleted in CRM.
    • Fixed: When a CRM destination component is using manually specified fields for the Upsert or Update action, and it is using BatchSize of 1, the component may fail when multiple matches are found even it is configured to Update All or Update One.
    • Fixed: In some very unique situations when CRM is not returning statuscode field values for no obvious reason even the field is requested in a query, if the destination component is configured to have statecode/statuscode fields mapped with the "Ignore Unchanged Fields" option checked, the destination component can fail when comparing the values.
    • Enhancement: When an incoming addressused value contains leading or trailing space characters, the destination component is now performing a trim action to remove those characters, otherwise CRM server will report an error when posted.
  • Microsoft Dynamics 365/NAV Components
    • Fixed: We fixed the automatic truncation of decimal numbers in the Dynamics 365/NAV source component.
  • Microsoft Dynamics 365/AX Components
    • Fixed: In some unique situations, you may get duplicate error messages in one error row when Redirect rows to error output option enabled.
  • Update: We have an updated license agreement in this release.

Version 8.0 - January 27, 2017

This is the official first release of the SSIS Integration Toolkit for Microsoft Dynamics 365. This toolkit combines the now retired SSIS Integration Toolkit for Microsoft Dynamics CRM, AX and NAV into one toolkit.

Note: Clients with SSIS Integration Toolkit for Microsoft Dynamics AX or NAV license keys will need a replacement key before upgrading to v8.0 or above. Please email [email protected] to receive your new key.

The following are the updates and enhancements made for each group of components.

  • Microsoft Dynamics 365/CRM Components
    • New: We added support for "Skipped Rows" output in the CRM destination component. This is also a breaking change, as a prior version (v7.4 or earlier) would not be able to process an SSIS package that contains a CRM destination component with the "Skipped Rows" output enabled.
    • New: You can now open a CRM view to be used to the FetchXML query in the CRM source component. Also added is the capability to load the query from a file.
    • New: Text Lookup feature now supports using SSIS variables in its Optional default value.
    • New: We added a ProxyMode option to Dynamics 365/CRM connection manager, which now supports three types of proxy mode: No Proxy, Auto-detect and Manual.
    • New: We added two new optional fields (CoalesceNonEmptyValues and PerformParentingChecks) for Merge action in CRM destination component.
    • Enhancement: We updated the support for Microsoft Dynamics 365 for Sales.
    • Fixed: When createdby field is mapped in the destination component for Create action, if the field is configured to use Text Lookup and the lookup has failed for a record, the error message in the Error Output can be misaligned with its actual row, if the destination component's Error Handling is set to "Redirect rows to error output".
    • Fixed: When working with CRM 4 or CRM 3, you might get "Object reference not set to an instance of an object error" when using <distinct> in FetchXML and the actual number of distinct results is greater than the batch size you have specified in the query.
  • Microsoft Dynamics 365/NAV Components
    • New: We added support for Microsoft Dynamics 365 for Financials and Microsoft Dynamics NAV 2017.
    • New: We added a ProxyMode option to Dynamics 365/NAV connection manager, which now supports three types of proxy mode: No Proxy, Auto-detect and Manual.
    • Fixed: The NAV source component does not save the Page Filtering and Supplementary Parameters properly through UI.
  • Microsoft Dynamics 365/AX Components
    • New: We added a new option to the AX destination component - Include Non-Editable Fields, which can be used to include all fields in AX.
    • New: We added a new option to the AX destination component - Bypass Table Method, which can be used to bypass the business logics implemented in table methods when writing to AX.
    • New: We added support of writing to AxaptaContainer type field in AX destination component.
    • Fixed: The AxRecId in the Default Output of the AX destination component may be generated in an incorrect data type format (Thanks to Henrik for reporting this).

For release notes prior to v8.0 please see the individual release note archives: