Release Notes

August 2026

We've made the following changes in v1.8.0:

• Added the transaction_accounting_lines_pass_through_columns variable, persisting chosen custom columns from the TRANSACTION_ACCOUNTING_LINE source table. These fields are brought into netsuite2__transaction_details. For more details, refer to the Passing Through Additional Fields section of the README.

• Fixed null conversion amounts for top-level subsidiaries missing a self-conversion exchange rate; rate now defaults to 1. Updates converted_amount values in netsuite2__transaction_details, netsuite2__income_statement, and netsuite2__balance_sheet.

• We've made 1 schema/data change in v1.8.0 (1 possible breaking change):

  Data Model(s)	Change type	Old	New	Notes
  stg_netsuite2__accounting_book_subsidiaries stg_netsuite2__accounting_book_subsidiaries_tmp	Removed model			Deprecated in v0.9.0 and unused in downstream models. Now fully sunset.

  A --full-refresh is recommended after upgrading.

We've updated the following quickstart data model packages to add DuckDB as a supported destination:

June 2026

v1.7.0

Under the Hood

• Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
• Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

v1.6.1

Bug Fix

• Fixes a Snowflake runtime error in netsuite2__transaction_details caused by timestamp datatype mismatches.

May 2026

v1.6.0

Schema/Data Changes (--full-refresh required after upgrading)

5 total changes • 2 possible breaking changes

Feature Update

• Adds Additional Customer Columns (customers_pass_through_columns in dbt Core) and Additional Item Columns (items_pass_through_columns in dbt Core) to Quickstart, persisting chosen custom columns from the CUSTOMER and ITEM source tables. These fields are brought into netsuite2__transaction_details.

April 2026

v1.5.1

Bug Fix

• Fixes a run error in netsuite2__balance_sheet that can occur when the Additional Account Columns (accounts_pass_through_columns) variable is configured.

v1.5.0

Feature Update

• Adds new variables to aggregate the netsuite2__balance_sheet and netsuite2__income_statement models, removing transactions and transaction lines from their granularity. By default, these models will continue to output data at the transaction line level. (PR #193)
  • netsuite2__aggregate_balance_sheet (default: false) When set to true:
    • netsuite2__balance_sheet outputs data at the account + accounting_period + subsidiary + account_category grain.
    • The primary key (balance_sheet_id) is hashed on (accounting_period_id, account_name, account_id, subsidiary_id, account_category, source_relation), plus to_subsidiary_id and accounting_book_id if included.
    • balance_sheet_transaction_detail_columns pass-through columns are ignored.
    • netsuite2__balance_sheet is run as a table instead of incrementally.
  • netsuite2__aggregate_income_statement (default: false) When set to true:
    • netsuite2__income_statement outputs data at the account + accounting_period + department + location + class grain.
    • The primary key (income_statement_id) is hashed on (accounting_period_id, account_name, subsidiary_id, department_id, location_id, class_id, source_relation), plus to_subsidiary_id and accounting_book_id if included.
    • income_statement_transaction_detail_columns pass-through columns are ignored.
    • netsuite2__income_statement is run as a table instead of incrementally.
• Adds support for Fivetran's history mode for the Netsuite2 source tables that currently support it (PR #195). When history mode is enabled in your Fivetran connector, the staging models below now filter on _fivetran_active to include only current, active records. Users without history mode enabled are unaffected, while users with history mode will see a drop in records (full refresh recommended):
  • stg_netsuite2__accounting_books
  • stg_netsuite2__accounting_periods
  • stg_netsuite2__accounts
  • stg_netsuite2__currencies
  • stg_netsuite2__customer_subsidiary_relationships
  • stg_netsuite2__customers
  • stg_netsuite2__departments
  • stg_netsuite2__employees
  • stg_netsuite2__entities
  • stg_netsuite2__entity_address
  • stg_netsuite2__items
  • stg_netsuite2__jobs
  • stg_netsuite2__location_main_address
  • stg_netsuite2__locations
  • stg_netsuite2__subsidiaries
  • stg_netsuite2__transactions
  • stg_netsuite2__vendor_categories
  • stg_netsuite2__vendor_subsidiary_relationships
  • stg_netsuite2__vendors

Only currently active records are included, while inactive records are filtered out. Please open a Feature Request if you would like historical records to be persisted.

Under the Hood

• Adds partition_by_source_relation() macro to avoid constant expression errors in Redshift.
• Limits the current accounting period from consistency data validation tests.
• Consolidates duplicative joins in netsuite2__balance_sheet
• Adds _fivetran_active to the get_netsuite2_*_columns() macros and src_netsuite2.yml source definitions for all 19 affected tables.
• Documents _fivetran_active in models/docs.md.

v1.4.1

Bug Fix

• Fixes the adapter.dispatch() call in the netsuite_union_relations macro, which was incorrectly dispatching to the zendesk namespace instead of netsuite.

January 2026

v1.4.0

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

v1.3.0

Schema/Data Change

2 total changes • 2 possible breaking changes

Feature Update

• When netsuite2__using_to_subsidiary is enabled, netsuite2__balance_sheet applies each transaction’s to_subsidiary fiscal calendar. If to_subsidiary is null, the model falls back to the fiscal calendar of the transaction’s subsidiary_id.
• Increases the required dbt version upper limit to v3.0.0

Under the Hood

• Adds full_name column to the get_accountingperiodfiscalcalendars_columns macro to support the new staging model field.
• Updates integration test seed data to include sample full_name values for testing the new functionality.
• In netsuite2__balance_sheet, combines variables netsuite2__using_to_subsidiary and netsuite2__using_exchange_rate into using_to_subsidiary_and_exchange_rate to simplify configuration.

November 2025

v1.2.1

Quickstart Update

• Adds netsuite2__entity_subsidiary_relationships to the public_models section of the quickstart.yml, so it is available to run in Quickstart for Fivetran customers.

v1.2.0

Schema/Data Change (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Documentation

• Enhanced documentation for amount fields in netsuite2__transaction_details and netsuite__transaction_details to clarify that the sign is flipped for income and other income accounts to follow accounting conventions. All other accounts retain their original sign.

October 2025

v1.1.0

Schema/Data Change

7 total changes • 2 possible breaking changes

Feature Update

• Union Data Functionality: This release supports running the package on multiple Netsuite source connections. See the README for details on how to leverage this feature.
• Entity-Subsidiary Relationships: New end model netsuite2__entity_subsidiary_relationships provides a unified view of both customer and vendor subsidiary relationships with enhanced metadata including currency information. Unions and enhances data from stg_netsuite2__customer_subsidiary_relationships and stg_netsuite2__vendor_subsidiary_relationships.
• Nexus Support: Adds comprehensive support for Netsuite nexus data through new staging model stg_netsuite2__nexuses with configurable pass-through columns. See the README for instructions on how to configure them.
• Adds Streamlit example to the README. See the README for more details.

Under the Hood

• Updates integration tests configuration and seed data references
• Updates the get_*_columns macros to return only the columns referenced by the corresponding staging model.

Contributors:

• @jmongerlyra (PR #171)
• @fivetran-poonamagate (PR #104)