Database Historical Sync Progress
You can now monitor your database historical sync progress in the status tab of your Fivetran dashboard. The status tab displays the table that is currently being synced as well as the number of tables that have finished syncing. This feature is available for all our database connectors.
Box is an online file sharing and cloud content management service for businesses.
Sage Intacct provides cloud-based accounting and financial management applications for small to mid-size organizations.
We have added two new tables,
USER_ALIAS. See Braze's Export User endpoint documentation for more information.
We have also created foreign key relationships to the following tables that reference the primary key column
user_id of the
We have added a new column,
mac_address, to the
We now support partitioning for update queries. Now, during an update operation, if your partition key is based on the destination primary key, we scan only the corresponding partitions instead of scanning the full table. We are gradually rolling out this new feature to all existing customers. If you'd like to enable this feature on your destination, contact our support team.
Facebook Ad Insights
You can now opt to specify no attribution window or select a single attribution window when you configure the connector. Depending on your requirements, on the connector setup form, set both or either of the Click Attribution Window and View Attribution Window fields to NONE.
Now we perform a table resync whenever a field is added to or removed from a custom table. Previously, we only used incremental and rollback syncs, which may have caused incorrect metrics values being displayed in the table and unwanted report segmentation inconsistencies when the field set was changed.
Google Search Console
The Google Search Console connector now supports the priority-first sync. The Google Search Console's priority-first sync fetches the most recent 30 days of data from the reporting tables. To learn more, see our priority-first sync documentation.
We have made our syncs more resilient to server failures from Greenhouse. If we can't connect to Greenhouse's servers during our syncs, we now retry the connection 3 times before the sync fails. Previously, our syncs failed immediately.
We now support future timestamp values in the
ENGAGEMENT_MEETING table. If you previously synced future timestamp values, re-sync the table to ensure data integrity.
We have improved incremental sync performance for databases which have many changes in collections that are not included in the sync.
We have added a slow sync notification on the connector dashboard for the re-imported tables. We now notify you about a sync’s start and completion for the tables that we re-import once a week and the tables you manually re-sync.
We now sync unparsable DATERANGE values (such as
10000-01-01) to the destination as null values.
We now mask the characters you enter in the API Key field of the connector setup form. We have changed the API Key field type from
PasswordField to improve security.
We have added support for
marketing.read API permission for our SendGrid Legacy accounts. You can now retrieve data from both legacy and new SendGrid marketing campaigns. We have also enabled backward compatibility. You can execute the queries designed for the old schema without any modifications on the new data.
We have added support for
marketing_campaign.read API permission for our SendGrid New accounts. You can now retrieve data from both new and legacy SendGrid marketing campaigns.
We now support two new fields,
true_tstamp. See Snowplow Analytics' documentation for more information about timestamps.
We have replaced the
dvce_tstamp field with the
dvce_created_tstamp field. We will deprecate the replaced field after January 10, 2021. Be sure to update your queries with the new field name before we remove the old field.
We have modified our sync strategy to skip a table’s rows if the
fact_conversion_counting column is empty. We sync the skipped rows after the
fact_conversion_counting column is populated with the final values to avoid duplicate data rows.
REST API Improvements
Displaying patch settings in standard config response
We have made changes to all public API endpoints that return the table and column configs as a response. Now you can see patch settings information for tables and columns in the response. It may help you understand whether you are allowed to enable or disable sync for them in the connector standard config. See the documentation for the following endpoints to learm more about the patch settings:
- Retrieve a Connector Schema Config
- Retrieve source table columns config
- Reload a connector schema config
- Modify a connector schema config
- Modify a connector database schema config
- Modify a connector table config
- Modify a connector column config