Skip to content

v0.13.0 dbt_netsuite

Latest
Compare
Choose a tag to compare
@fivetran-data-model-bot fivetran-data-model-bot released this 30 Apr 23:58
· 6 commits to main since this release
d16bb4a

For Netsuite2, PR #116 includes the following updates:

🚨 Breaking Changes 🚨

⚠️ Since the following changes are breaking, a --full-refresh after upgrading will be required.

  • Performance improvements:

    • Snowflake, Postgres, and Redshift destinations:
      • Added an incremental strategy for the following models:
        • int_netsuite2__tran_with_converted_amounts
        • netsuite2__balance_sheet
        • netsuite2__income_statement
        • netsuite2__transaction_details
    • Bigquery and Databricks destinations:
      • Due to the variation in pricing and runtime priorities for customers, by default we chose to materialize these models as tables instead of incremental materialization for Bigquery and Databricks. For more information on this decision, see the Incremental Strategy section of the DECISIONLOG.
      • To enable incremental materialization for these destinations, see the Incremental Materialization section of the README for instructions.
  • To reduce storage, updated the default materialization of the upstream staging models to views. (See the dbt_netsuite_source CHANGELOG for more details.)

🎉 Features

  • Added a default 3-day look-back to incremental models to accommodate late arriving records, based on the _fivetran_synced_date of transaction records. The number of days can be changed by setting the var lookback_window in your dbt_project.yml. See the Lookback Window section of the README for more details.
  • Added macro netsuite_lookback to streamline the lookback calculation.

Under the Hood:

  • Added integration testing pipeline for Databricks SQL Warehouse.
  • Included auto-releaser GitHub Actions workflow to automate future releases.

For Netsuite2, PR #114 includes the following updates:

Features

  • Added the following columns to model netsuite2__transaction_details:

    • department_id
    • entity_id
    • is_closed
    • is_main_line
    • is_tax_line
    • item_id
    • transaction_number
  • ❗Note: If you have already added any of these fields as passthrough columns to the transactions_pass_through_columns, transaction_lines_pass_through_columns, accounts_pass_through_columns, or departments_pass_through_columns vars, you will need to remove or alias these fields from the var to avoid duplicate column errors.

  • Removed the unnecessary reference to entities in the netsuit2__transaction_details model.

📝 Documentation Update 📝

  • Updated DECISIONLOG with our reasoning for why we don't bring in future-facing transactions and leave the converted_amount in transaction details empty. (#115)

Contributors:

Full Changelog: v0.12.0...v0.13.0