Release Notes

June 2023

We have changed the sync strategy of the TRANSACTION_TRACKING_NUMBERS table. We now re-import the TRANSACTION_TRACKING_NUMBERS table based on the table import duration:

If the duration is less than or equal to 20 seconds, we re-import the table in every sync.
If the duration is more than 20 seconds, we re-import the table twice daily.

April 2023

For Netsuite version 2023.1 or above, we now the TransactionAccountingLine table to capture updates. This increases the speed of your syncs and consumes lesser MAR. For older versions, we continue to this table.

March 2023

The NetSuite2.com data source for our NetSuite SuiteAnalytics connector is now . .

We now re-import the POSTING_ACCOUNT_ACTIVITY table in every sync.

December 2022

We now the SystemNote table for the Netsuite2.com data source. We don't capture deletes or updates because the table is immutable.

August 2022

We have added support for CLOB data type. We now convert the data to STRING data type in your destination tables. We are gradually rolling out this feature to all existing connectors.

Our dbt-Core* compatible data models for NetSuite SuiteAnalytics now support the NetSuite2.com data source. Find the models in or . Learn more about our dbt Core integration in our *.

* 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.

April 2022

You can now use the to configure your NetSuite SuiteAnalytics connector. This feature is in . For more information, see our .

March 2022

We have added support for the NetSuite2.com data source. We are gradually rolling out this feature to all our existing customers.

You can now create new NetSuite connectors that sync data from the NetSuite2.com data source into your destination.

NOTE: If your NetSuite account provides access to both data sources, you can sync data from both data sources using a separate connector for each data source. However, we do not support switching data sources for existing NetSuite connectors.

August 2020

We have released pre-built, dbt Core-compatible data models for NetSuite SuiteAnalytics. Find the models in or . Learn more about our dbt Core integration in our *.

* 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.

We have modified our sync strategy for incremental tables. Now, during the incremental update, we restrict the latest re-import range to the maximum primary key value. Previously, during the incremental update, we didn’t restrict the range, which caused high MAR (monthly active rows) consumption. We are gradually rolling out this change to all existing customers. If you'd like to use the updated strategy immediately, .

July 2020

We have changed the sync strategy for the incremental tables that have the _fivetran_index column as a primary key. We are gradually rolling out this change to all existing customers.

We have changed the sync strategy for the re-import tables that have the _fivetran_index column as a primary key. We are gradually rolling out this change to all existing customers.

We have also changed the sync strategy of the _fivetran_index column. Now, we use a monotonically increasing value for the _fivetran_index column that is specific to each primary key. Previously, we used a monotonically increasing value that was specific to the full table. We have implemented the modified sync strategy for the following tables:

BILLING_SCHEDULE
ITEM_LOCATION_MAP
ITEM_PRICES
ITEM_VENDOR_PRICING
POSTING_ACCOUNT_ACTIVITY
REVRECSCHEDULELINES
TRANSACTION_SHIPPING_GROUPS
TRANSACTION_TRACKING_NUMBERS

We are gradually rolling out this change to all existing customers.

We now use the DELETED_RECORDS table to capture deleted records for tables that have a single primary key and are updated incrementally. Previously, during the incremental update, we imported ranges, which caused high MAR (monthly active rows) consumption. We are gradually rolling out this change to all existing customers.

We have removed the Data Source field from the connector setup form because we only support NetSuite.com as a data source.

We have changed our sync strategy for tables that have a single primary key and are updated incrementally. We now use the data_last_modified column to retrieve updates and new records, and we re-import ranges only to capture deletes. We are gradually rolling out this change to all existing customers.

June 2020

We now create empty tables in the destination even if the source tables are empty (contain only Null values).

We now support NetSuite 2020 Release 1 API version. We will gradually roll out this change to all the existing customers.

We now add a _fivetran_synced column while syncing empty tables and columns from the source.

We have added the following new tables:

ADDRESSES
BILL_OF_MATERIALS
BOM_REVISION_COMPONENTS
BOM_REVISIONS
CURRENCY_EXCHANGE_RATE_TYPES
CURRENCY_EXCHANGE_RATES
EMPLOYEE_CURRENCY_MAP
INBOUND_SHIPMENTS
ITEM_COLLECTION_ITEM_MAP
ITEM_COLLECTIONS
ITEM_PRICE_HISTORY
LOCATION_COSTING_GROUPS
LOCATION_COSTING_GRP_LOCATIONS
PURCHASE_CHARGE_RULES
RESOURCE_GROUP_ENTITY_MAP
RESOURCE_GROUPS
SUBSCRIPTION_LINE_REVISIONS
TRANSACTION_HISTORY
UNLOCKED_TIME_PERIODS

April 2020

We will implement a new and modified sync strategy for a subset of the supported NetSuite tables. This strategy will ensure that our syncs capture the deleted and modified records. for the complete list of tables that uses the modified sync strategy.

NetSuite stopped updating timestamps from child records to parent records, and this impacted our current sync strategy.

We will gradually roll out this change to all the existing customers. As part of the deployment, we will re-sync the tables for which we have changed the sync strategy.

November 2019

We have changed reimport frequency for reimported tables:

Table Import Duration	Import Frequency
20 secs or less	Re-import in every sync
Between 20 secs and 60 mins	Re-imported twice a day
More than 60 mins	Re-imported once a week

Tables that take longer than 20 seconds to import get marked as not recommended on the dashboard and include a message on how frequently Fivetran syncs them. For more information, see our .

March 2019

We added several new tables following the NetSuite 2018.2 release. Their behavior is specified below.

ACCOUNT_PERIOD_ACTIVITY_PE will not be synced separately because it contains a subset of the information in the larger table POSTING_ACCOUNT_ACTIVITY_PE which we already sync.
The following tables will be re-imported based on :
- CUSTOMER_SUBSIDIARY_MAP
- POSTING_ACCOUNT_ACTIVITY_PE
- PRICE_BOOKS
- PRICE_BOOK_LINE_INTERVALS
- PRICE_PLANS
- PRICE_TIERS
- REVENUE_PLAN_VERSIONS
- STANDARD_COST_COMPONENTS
The following tables will be updated incrementally:
- BILLING_SUBSCRIPTIONS
- EXPENSE_AMORTIZATION_RULES
- EXPENSE_PLANS
- GLOBAL_INVENTORY_RELATIONSHIPS
- PLANNED_STANDARD_COSTS
- SUBSCRIPTION_CHANGE_ORDERS
- SUBSCRIPTION_PLANS
BILLING_SUBSCRIPTION_LINES and SUBSCRIPTION_PLAN_LINES are sub tables of BILLING_SUBSCRIPTIONS and SUBSCRIPTION_PLANS respectively and will be updated along with the parent tables.

November 2018

You can now trigger re-syncs of individual tables from your Fivetran dashboard:

Customer triggered resyncs!

The re-sync button appears when you hover your cursor over the row that contains the table name.

This feature is available for the following connectors:

DynamoDB
MongoDB
MySQL
NetSuite SuiteAnalytics
Oracle
PostgreSQL
Salesforce
SQL Server
Zuora

We have fixed the incremental update of child tables. All child tables of child tables will also be updated recursively. For example, if the TRANSACTIONS table is updated, then its child table TRANSACTION_LINES will be updated, along with TRANSACTION_LINES's own child tables BIN_NUMBER and BIN_NUMBER_COUNTS.

October 2018

We have released service version 3 of the NetSuite SuiteAnalytics connector, which includes the following new features:

Tables that can't be incrementally updated can now be re-imported. The frequency with which we update these re-import tables is based on how fast we can ingest them from NetSuite. For more information, see our
The ITEM_LOCATION_MAP re-import table will update every sync. To see the duration of each table import, you can refer to the table warning field on the Schema tab of your Fivetran dashboard's Connector page.
We can now upload records for tables where the primary key column contains null values. For more information, see our

June 2018

The _fivetran_synced field will now reflect the actual moment when we insert or update rows, rather than the sync start time.

May 2018

We have updated the JDBC driver to version 7.20.50.

We no longer sync the SUBSCRIPTION_CO_LINES table.