dbt_netsuite v0.7.0

🚨 Breaking Changes 🚨:

PR #53 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
• 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"].

dbt_netsuite v0.6.3

Happy Monday and International Ninja Day 🥷

This release of the dbt_netsuite package includes the following updates:

Bug Fixes 🐞

• Adjustment within the int_netsuite2_tran_lines_w_accounting_period model to correctly filter only posting accounts. Previously this filter filtered for only non-posting accounts. In order to replicate a true income statement, the posting accounts should only be included downstream. (#56)

dbt_netsuite v0.6.2

PR #48 includes the following updates to the dbt_netsuite package:

Features 🎉 (affects Netsuite2 users only)

• Introduces the netsuite2__multibook_accounting_enabled and netsuite2__using_vendor_categories variables to disable their related source tables and downstream models.
  • netsuite2__multibook_accounting_enabled is True by default. Set it to False if you do not use the Multi-Book Accounting feature in Netsuite and/or do not have the accountingbook and accountingbooksubsidiaries source tables.
  • netsuite2__using_vendor_categories is True by default. Set it to False if you do not categorize vendors in Netsuite and/or do not have the vendorcategory source table.

Bug Fixes 🐞

• Fixes the grain at which the netsuite__transaction_details model is tested (Netsuite.com users only).

dbt_netsuite v0.6.1

dbt_netsuite v0.6.1

Bug Fixes 🐞

• Properly applies new passthrough column logic to allow for the use of alias and transform_sql (see v0.6.0 below). (#43)

dbt_netsuite v0.6.0

dbt_netsuite v0.6.0

🎉 Netsuite2 Compatibility 🎉

PR #41 includes the following update to the dbt_netsuite package:

🚨 Breaking Changes 🚨

• The declaration of passthrough variables within your root dbt_project.yml has changed. To allow for more flexibility and better tracking of passthrough columns, you will now want to define passthrough columns in the following format:

This applies to all passthrough columns within the dbt_netsuite package and not just the customers_pass_through_columns example.

vars:
  customers_pass_through_columns:
    - name: "my_field_to_include" # Required: Name of the field within the source.
      alias: "field_alias" # Optional: If you wish to alias the field within the staging model.
      transform_sql: "cast(field_alias as string)" # Optional: If you wish to define the datatype or apply a light transformation.

Features 🎉

• Addition of the netsuite_data_model variable. This variable may either be netsuite (the original Netsuite.com connector endpoint) or netsuite2 (the new Netsuite2 connector endpoint).
  • The variable is set to netsuite by default. If you wish to run the data models for the Netsuite2 connector, you may simply change the variable within your root dbt_project.yml to netsuite2.
• Postgres compatibility!
• Added identifier variables to each Netsuite.com and Netsuite2 source to enable dynamic source-table adjustments.
• Applied schema level tests to each Netsuite2 end model to ensure data validation.
• README updates for easier navigation and package use

dbt_netsuite 0.5.0

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
  • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
  • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
• Upgrades the package dependency to refer to the latest dbt_netsuite_source. Additionally, the latest dbt_netsuite_source package has a dependency on the latest dbt_fivetran_utils. Further, the latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

Previous Version Fields Added

Happy Friday!

This release of the dbt_netsuite Fivetran package includes the following non-breaking updates:

• Addition of the customer_external_id and class_full_name fields within thenetsuite__transaction_details model as well as the subsidiary_id, subsidiary_full_name, and subsidiary_name fields within the netsuite__income_statement model. These fields were included in a previous release of this package which were inadvertently removed in an upgrade.

Thanks to the call out and PR by @Norina-Sun to help us identify adding this field back in. 🎉

dbt 0.20.0 Compatibility

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.

README Variable Typo Fix

✏️ README Variable Typo Fix ✏️

This release includes the following non-breaking changes:

• Fixes a typo within the netsuite_database and netsuite_schema variable declarations within the README. PR #30

Limit in Balance Sheet Removed

Happy Monday!

This release includes the following non-breaking changes:

• Removes a holdover limit within the final netsuite__balance_sheet statement that was used for testing. Issue #29