v1.6.0-a1 dbt_netsuite

PR #200 includes the following updates:

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

2 total changes • 0 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
netsuite2__transaction_details netsuite2__entity_subsidiary_relationships	Filter on VENDOR data	Soft-deleted records excluded	Soft-deleted records included
netsuite2__transaction_details	New field		amount_linked	The amount applied against another transaction (e.g. a payment applied to an invoice).

dbt Core/Additional Details

5 total changes • 2 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
stg_netsuite2__customers	New fields		is_inactive, comments, url, created_at	Breaking Change: Remove from customers_pass_through_columns if currently included.
stg_netsuite2__entities	New fields		date_created, _fivetran_deleted	Breaking Change: Remove from entities_pass_through_columns if currently included.
stg_netsuite2__transaction_accounting_lines	New field		amount_linked
stg_netsuite2__transaction_lines	New field		_fivetran_deleted
stg_netsuite2__transactions	New field		_fivetran_deleted	Soft-deleted records are still filtered out.

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.

Full Changelog: v1.5.1...v1.6.0-a1

v1.5.1 dbt_netsuite

PR #199 includes the following updates:

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.

Full Changelog: v1.5.0...v1.5.1

v1.5.0 dbt_netsuite

This release includes the following updates:

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.

Full Changelog: v1.4.1...v1.5.0

v1.4.1 dbt_netsuite

PR #197 includes the following update:

Bug Fix

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

Full Changelog: v1.4.0...v1.4.1

v1.5.0-a2 dbt_netsuite

PR #193 includes the following updates:

Feature Update

• Adds new variables to roll the netsuite2__balance_sheet and netsuite2__income_statement models up to the account and accounting period grain (and subsidiary and accounting book if those features are enabled). By default, these models will continue to output data at the transaction line level:
  • netsuite2__aggregate_balance_sheet (default: false): Set to true to roll netsuite2__balance_sheet up to the account and accounting period grain. When aggregated, balance_sheet_transaction_detail_columns pass-through columns are ignored and the model will be run as a table instead of incrementally.
  • netsuite2__aggregate_income_statement (default: false): Set to true to roll netsuite2__income_statement up to the account and accounting period grain. When aggregated, income_statement_transaction_detail_columns pass-through columns are ignored and the model will be run as a table instead of incrementally.

Under the Hood

• Adds partition_by_source_relation() macro to avoid constant expression errors in Redshift.

Full Changelog: v1.5.0-a1...v1.5.0-a2

v1.5.0-a1 dbt_netsuite

PR #193 includes the following updates:

Schema/Data Change

3 total changes • 3 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
netsuite2__balance_sheet	Default Materialization	Incremental	Table	Can still be run incrementally by setting the netsuite2__balance_sheet_use_incremental variable to true.
netsuite2__income_statement	Default Materialization	Incremental	Table	Can still be run incrementally by setting the netsuite2__income_statement_use_incremental variable to true.
netsuite2__transaction_details	Default Materialization	Incremental	Table	Can still be run incrementally by setting the netsuite2__transaction_details_use_incremental variable to true.

Feature Update

• Adds the option to aggregate the netsuite2__balance_sheet and netsuite2__income_statement past transactions and to the account and accounting period grain.
  • To do so, set the following variable(s) to false. Both default to true, preserving one row per transaction line with transaction_id and transaction_line_id in the output:

vars:
    netsuite2__balance_sheet_transaction_level: false # True by default. Set to false to roll up to account/period level in netsuite2__balance_sheet.
    netsuite2__income_statement_transaction_level: false # True by default. Set to false to roll up to account/period level in netsuite2__income_statement.

Note: When set to false, any columns passed via balance_sheet_transaction_detail_columns or income_statement_transaction_detail_columns are ignored.

Under the Hood

• Adds partition_by_source_relation() macro to avoid constant expression errors in Redshift.

Full Changelog: v1.4.0...v1.5.0-a1

v1.4.0 dbt_netsuite

PR #190 includes the following updates:

Documentation

• Updates README with standardized Fivetran formatting.

Under the Hood

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

Full Changelog: v1.3.0...v1.4.0

v1.4.0-a2 dbt_netsuite

Schema/Data Change

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
int_netsuite2__tran_with_converted_amounts	Materialization	Table (all warehouses except BigQuery) Ephemeral (BigQuery)	Ephemeral (all warehouses)	Breaking change: Reverts the materialization change from v1.4.0-a1. The model now uses ephemeral materialization for all warehouse platforms, simplifying configuration and reducing storage overhead. Removes warehouse-specific materialization logic and partitioning configuration.

Full Changelog: v1.4.0-a1...v1.4.0-a2

v1.4.0-a1 dbt_netsuite

PR #189 includes the following updates:

Schema/Data Change

3 total changes • 2 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
netsuite2__balance_sheet netsuite2__income_statement netsuite2__transaction_details	Materialization	Incremental (PostgreSQL, Redshift, Snowflake) Table (Bigquery, Databricks, Spark)	Table (all warehouses by default)	Breaking change: PostgreSQL, Redshift, and Snowflake users will see materialization change from incremental to table by default. To restore incremental materialization, set netsuite2__using_incremental: true. This change provides consistent default behavior across all warehouse platforms and gives users explicit control over incremental materialization.
netsuite2__balance_sheet netsuite2__income_statement netsuite2__transaction_details	Configuration	cluster_by: ['transaction_id']	No clustering	Breaking change: Removes cluster_by configuration to improve model build performance. Clustering overhead on high-cardinality keys was causing performance degradation. Partitioning by _fivetran_synced_date provides sufficient query optimization.
int_netsuite2__tran_with_converted_amounts	Materialization	Ephemeral (all warehouses)	Table (all warehouses except BigQuery)	Materializes as a table for PostgreSQL, Redshift, Snowflake, Databricks, and Spark with partitioning by _fivetran_synced_date. BigQuery remains ephemeral. This update is intended to improve overall build performance.

Feature Update

• Introduces netsuite2__using_incremental variable to provide simplified control over incremental materialization for Netsuite2 end models. Users can now enable incremental materialization with a single variable instead of configuring each model individually. When enabled, uses merge strategy for Bigquery, Databricks, and Spark, and delete+insert strategy for PostgreSQL, Redshift, and Snowflake. See the README for configuration details.

Under the Hood

• Removes redundant join condition and transactions_with_converted_amounts.source_relation = transactions_with_converted_amounts.source_relation in netsuite2__transaction_details for improved code clarity.
• Updates integration test seed data with current date values and additional test records.

Documentation

• Updates README and DECISIONLOG to document the new netsuite2__using_incremental variable and incremental materialization strategies for different warehouse platforms.

Full Changelog: v1.3.0...v1.4.0-a1

v1.3.0 dbt_netsuite

PR #187 includes the following updates:

Schema/Data Change

2 total changes • 2 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
netsuite2__balance_sheet netsuite2__income_statement netsuite2__transaction_details stg_netsuite2__accounting_period_fiscal_cal	New column		accounting_period_full_name	Adds the full name field from the accounting period fiscal calendar source table, providing descriptive period names like "FY2023 : Q1 2023".

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.

Contributors

• @jmongerlyra (PR #183)

Full Changelog: v1.2.1...v1.3.0