Release Noteslink
November 2020link
We now create an additional table STRINGMAP to sync the string values and the mapping information of your picklist attributes. Previously, we used to sync only the code values of the picklist attributes. See our documentation for more information.
October 2020link
We have expanded the public API endpoints Create a Connector and Modify a Connector. Now you can authorize the following connectors by adding the auth section to payloads:
August 2020link
We now automatically re-sync a table when we receive an expired token error response for the table from Microsoft.
April 2020link
You can now configure your Microsoft Dynamics 365 CRM connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
We now create empty tables in the destination even if the source tables are empty (contain only Null values).
March 2020link
We have simplified setup for our Microsoft Dynamics 365 CRM connector. We now only require the schema name, domain name and resource URL. You no longer need to register an app with Azure, nor do we need your application ID or client secret.
March 2019link
Fivetran now syncs binary data from Dynamics 365 Sources.
February 2019link
The tables that do not support Change Tracking will be shown as Not Recommended in Standard Config.
January 2019link
The setup form for the Microsoft Dynamics 365 CRM now contains two additional fields, Application ID and Client Secret. We have also updated our documentation to include instructions for registering an application on the Azure Portal.