Release Notes

April 2025

We have resolved a data integrity issue in the Sage Intacct connector that impacts the GLACCOUNTBALANCE table. We have updated the primary key RECORDNO calculation for this table.

Earlier, we calculated the primary key as a hash of the following columns:

• accountno
• bookid
• classid
• customerid
• departmentid
• employeeid
• itemid
• location_id
• period
• projectid
• vendorid
• warehouseid

Now, we calculate the primary key as a hash of the following columns:

• accountno
• accountrec
• accounttitle
• bookid
• classdimkey
• classid
• classname
• contractdimkey
• contractid
• contractname
• createdby
• currency
• customerdimkey
• customerid
• customername
• departmentid
• employeedimkey
• employeeid
• employeename
• endbal
• forbal
• gldimcompensation_type
• gldimservice_line
• itemdimkey
• itemid
• itemname
• location_id
• locationno
• modifiedby
• openbal
• period
• projectdimkey
• projectid
• projectname
• recordno
• record_url
• taskdimkey
• taskid
• taskname
• totadjcredit
• totadjdebit
• totcredit
• totdebit
• vendordimkey
• vendorid
• vendorname
• whencreated

To correct historical data in your destination:

• You can initiate a free resync for the GLACCOUNTBALANCE table until May 5, 2025, from Fivetran.
• If you choose not to resync, only incremental data from April 17, 2025, will reflect the updated RECORDNO calculation.

NOTE:

• Resyncs will result in a large number of API calls to Sage Intacct, which may lead to additional charges at the source as per the Sage Intacct API pricing model.
• GLACCOUNTBALANCE is a high-volume table, so sync times may increase during the resync.
• You might notice an increase in MAR as we synced previously missed rows.

February 2025

We no longer sync the GL_DETAIL table as a child table of the GL_BATCH table. We now sync the GL_DETAIL table as a parent table without any child tables.

We have also changed the sync strategy for the GL_DETAIL table. We no longer capture the deletes for the GL_DETAIL table through incremental syncs.

We now support syncing custom fields for the SO_DOCUMENT and SO_DOCUMENT_ENTRY tables. To sync these fields, you must enable the SO_DOCUMENT_PARAMS table in Sage intacct.

We have updated the Quickstart packages for the following connectors:

• Ad Reporting data model connectors to version 0.5.0
• Amplitude to version 0.6.0
• Apple App Store to version 0.5.0
• App reporting data model connectors to version 0.5.0
• Asana to version 0.8.3
• HubSpot to version 0.21.0
• Sage Intacct to version 0.6.0
• Shopify to version 0.17.0
• Snapchat Ads to version 0.8.0
• Stripe to version 0.16.1
• Zuora to version 0.3.2

December 2024

We have added existing columns, location_id and department_id, to the composite primary key in the USERRESTRICTION table.

August 2024

We have updated the connector's sync strategy. We now re-sync the past 16 days' worth of data every Saturday, compared to the previous 10 days. As a result, you may observe an increase in your Monthly Active Rows (MAR) usage.

July 2023

Our Sage Intacct connector is now generally available.

May 2023

We have fixed a bug where we didn't sync Sage Intacct custom objects. We have updated our sync mechanism to now sync custom objects.

If you don't want to sync custom objects, deselect the custom object tables from the Schema tab of your connector details page.

April 2023

We have changed the new connector creation process for Sage Intacct connectors. We now use a different authentication method for Sage Intacct connectors created after April 20, 2023. We now require Sender ID and Sender Password for authentication. For more information, see our Sage Intacct Setup Guide.

We will support the existing Sage Intacct connectors that use the Fivetran-provided sender ID until April, 2024. You can also opt to migrate your existing connector to the new authentication process.

March 2022

We have released pre-built, dbt Core*-compatible data models for Sage Intacct. Find the models in Fivetran's dbt hub. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

*dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

February 2022

We have implemented a new custom strategy to capture deleted records because the Sage Intacct API doesn't offer a reliable mechanism to capture deletes. For more information about the strategy, see our Capture deletes documentation.

January 2022

Now, when you delete a record in your source table, we do the following:

• For a parent table, we mark the record as deleted in the destination table. We set the _fivetran_deleted column to TRUE.
• For a child table, we don't delete the record from the destination table.

Previously, we permanently deleted the record from the child table in your destination. For more information, see our documentation.

July 2021

You can now configure your Sage Intacct connector using the Fivetran REST API. This feature is available only for Standard and Enterprise accounts.

March 2021

We have added a new table, SODOCUMENTENTRY.

February 2021

Sage Intacct is a cloud-based financial management and services provider.

Read our Sage Intacct connector documentation.