v0.11.0 dbt_netsuite_source

PR #57 includes the following update:

Breaking Changes

• Casted specific timestamp fields across all staging models as dates where the Netsuite UI does not perform timezone conversion. Keeping these fields as type timestamp causes issues in reporting tools that perform automatic timezone conversion.
  • As this will change the datatype of the underlying fields, this will require a --full-refresh for downstream incremental models.
• Existing fields that were converted from timestamp to date in the following stg_netsuite2__* models:

Table	Source Field Name	Field Alias
accounting_periods	startdate	starting_at
accounting_periods	enddate	ending_at
customers	firstorderdate	date_first_order_at
transactions	closedate	closed_at
transactions	duedate	due_date_at
transactions	trandate	transaction_date

• Adds additional commonly used fields within the stg_netsuite2__* models.

Table	Source Field Name	Field Alias
accounts	accountsearchdisplaynamecopy	display_name
customers	altname	alt_name
subsidiaries	iselimination	is_elimination
transaction_accounting_lines	exchangerate	exchange_rate
transaction_lines	eliminate	is_eliminate
transaction_lines	netamount	netamount
transactions	reversal	reversal_transaction_id
transactions	reversaldate	reversal_date
transactions	reversaldefer	is_reversal_defer

IMPORTANT: Nearly all of the affected models have pass-through functionality. If you have already been using passthrough column variables to include the above newly added fields (without aliases), you MUST remove the fields from your passthrough variable configuration in order to avoid duplicate column errors.

Feature Updates

• Introduced the stg_netsuite2__employees model to bring in data from the employee source table.
  • Since this model is only used by a subset of customers, we've introduced the variable netsuite2__using_employees to allow users who don't utilize the employee table in Netsuite2 the ability to disable that functionality within your dbt_project.yml. This value is set to true by default. Instructions are available in the README for how to disable this variable.

Under the Hood

• Created new seed data in integration_tests to support the new stg_netsuite2__employees model, as well as the new fields introduced into the new Netsuite2 staging models.

Contributors

• @jmongerlyra (PR #54)

Full Changelog: v0.10.1...v0.11.0

v0.10.1 dbt_netsuite_source

PR #51 includes the following update:

Feature Update

• Added the entities_pass_through_columns variable to be leveraged within the stg_netsuite2__entities model. This variable will allow users to pass through fields which are not natively included to the package staging model.
  • Removed fields from the get_entity_columns macro that are not brought into the stg_netsuite2__entities model to ensure that the passthrough feature works properly.

Contributors:

• @FrankTub (PR #51)

Full Changelog: v0.10.0...v0.10.1

v0.10.0 dbt_netsuite_source

PR #47 includes the following update:

🚨 Breaking Changes 🚨

• Added column _fivetran_synced_date to model stg_netsuite2__transactions for use in downstream models.
• To reduce storage, updated default materialization of staging models to views.

⚠️ Running a --full-refresh will be required if you have previously run these staging models as tables and get the following error:

Trying to create view <model path> but it currently exists as a table. Either drop <model path> manually, or run dbt with `--full-refresh` and dbt will drop it for you.

Under the Hood:

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

Full Changelog: v0.9.0...v0.10.0

v0.9.0 dbt_netsuite_source

PR #42 includes the following update:

🚨 Breaking Changes 🚨:

• Addition of the currency field as currency_id within the stg_netsuite2__subsidiaries model.
  • This addition likely won't be breaking for a large number of users. However, if you are leveraging the subsidiaries_pass_through_columns variable and have included currency as a pass through column, you will experience a duplicate column error. We advise you remove the currency field as a pass through column to avoid runtime errors following this upgrade.

Contributors:

• @jmongerlyra (PR #41)

Full Changelog: v0.8.0...v0.9.0

v0.8.0 dbt_netsuite_source

🚨 Breaking Changes 🚨:

• Addition of the is_eliminate and special_account_type_id fields within the stg_netsuite2__accounts model. (PR #39 and PR #40)
  • This addition likely won't be breaking for a large number of users. However, if you are leveraging the accounts_pass_through_columns variable and have included either eliminate or sspecacct as a pass through columns then you will experience a duplicate column error. We advise you remove the eliminate and sspecacct fields as a pass through columns to avoid runtime errors following this upgrade.

Contributors:

• @jmongerlyra (PR #40)

Full Changelog: v0.7.0...v0.8.0

v0.7.0 dbt_netsuite_source

PR #36 includes the following update:

🚨 Breaking Changes 🚨:

• Brought in accounting_book_id (accountingbook) to the stg_netsuite2__consolidated_exchange_rates model.
  • Due to logic within the dbt_netsuite v0.8.1 package version, this update will result in an ambiguous columns error. Therefore, this update is treated as a breaking change.

Full Changelog: v0.6.3...v0.7.0

v0.6.3 dbt_netsuite_source

🎉 Feature Updates 🎉

PR #35 applies the following changes:

• Introduces variable netsuite2__using_exchange_rate to allow users who don't utilize exchange rates in Netsuite2 the ability to disable that functionality within your dbt_project.yml, since these models aren't being used.
• Note: If you are using the dbt_netsuite package, be sure to set it globally by inserting this code into your dbt_project.yml:

vars:
  netsuite2__using_exchange_rate: false

Full Changelog: v0.6.2...v0.6.3

v0.6.2 dbt_netsuite_source

🎉 Feature Updates 🎉

• Introduces the netsuite2__using_jobs variable in order to disable the stg_netsuite2__jobs model. Set netsuite2__using_jobs to False if you do not have the job table in your Netsuite2 schema (PR #30).

Contributors

• ropalloni (#29)

v0.6.1 dbt_netsuite_source

Bug Fixes

• In v0.6.0, we introduced pass through columns for the vendors and items tables. However, this update was only applied to the original Netsuite version of this package, and not Netsuite2 as well. These pass through columns are accessible in Netsuite2 data models (PR #27).

🎉 Feature Updates 🎉

• Now introducing...Databricks compatibility 🧱 (PR #26)

dbt_netsuite_source v0.6.0

🚨 Breaking Changes 🚨:

PR #24 includes the following breaking changes:

• Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
  • any_value
  • bool_or
  • cast_bool_to_text
  • concat
  • date_trunc
  • dateadd
  • datediff
  • escape_single_quotes
  • except
  • hash
  • intersect
  • last_day
  • length
  • listagg
  • position
  • replace
  • right
  • safe_cast
  • split_part
  • string_literal
  • type_bigint
  • type_float
  • type_int
  • type_numeric
  • type_string
  • type_timestamp
  • array_append
  • array_concat
  • array_construct
• For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
  • dbt.current_timestamp_backcompat
  • dbt.current_timestamp_in_utc_backcompat
• dbt_utils.surrogate_key has also been updated to dbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do a full-refresh for the most accurate data. For more information, please refer to dbt-utils release notes for this update.
• packages.yml has been updated to reflect new default fivetran/fivetran_utils version, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

Features

• Added the vendors_pass_through_columns variable to be leveraged within the stg_netsuite__vendors model. This variable will allow users to pass through fields which are not natively included to the package staging model. This variable is empty by default and may be overridden within a users root dbt_project.yml. (#23)
• Added the items_pass_through_columns variable to be leveraged within the stg_netsuite__items model. This variable will allow users to pass through fields which are not natively included to the package staging model. This variable is empty by default and may be overridden within a users root dbt_project.yml. (#23)