v0.9.3 dbt_salesforce_formula_utils

PR #101 includes the following updates:

🗒️ Documentation Update 🗒️

• Fivetran has deprecated support for the full_statement_version=false. We've removed mention of this obsolete method in the README.

🚇 Under the Hood 🚇

• Users will not see functional differences from v0.9.2. However, due to changes in the Fivetran Salesforce connector, users still utilizing the full_statement_version=false should expect formula field values to be null.

Contributors

• @raymondgh

Full Changelog: v0.9.2...v0.9.3

v0.9.2 dbt_salesforce_formula_utils

PR #96 includes the following updates:

🗒️ Documentation Update 🗒️

• Fivetran will be deprecating support for the full_statement_version=false config by October 1, 2023. We've highlighted this change to users of the package in the README.

🚇 Under the Hood 🚇

• Users still utilizing the full_statement_version=false config will receive a log message in their dbt run indicating deprecation of support for those options.

Full Changelog: v0.9.1...v0.9.2

v0.9.1 dbt_salesforce_formula_utils

Bugfix

• Databricks users faced a syntax error resulting from the sfdc_formula_view_sql macro not correctly compiling. This update adds the Databricks warehouse to a conditional in the macro that allows the sql to correctly compile. (PR #94) (PR #92)
• Postgres users faced a syntax error resulting from the sfdc_formula_view_sql macro not correctly compiling. This update adds the Postgres warehouse to a conditional in the macro that allows the sql to correctly compile. (PR #94)

Contributors:

• @corca (PR #92)

Full Changelog: v0.9.0...v0.9.1

v0.9.0 dbt_salesforce_formula_utils

This release of dbt_salesforce_formula_utils includes:

🎉 Feature Update 🎉

• Databricks compatibility! (#89)

Full Changelog: v0.8.2...v0.9.0

v0.8.2 dbt_salesforce_formula_utils

This release of dbt_salesforce_formula_utils includes:

Features

• Clarify Step 5 of the README that sfdc_exclude_formulas works only with Options 2 and 3. (#88)

Under the Hood:

• Renamed macro filename from sfdc_current_formula_fields to sfdc_current_formula_values to be consistent with its macro name. (#86)
• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (#82)
• Updated the pull request templates. (#82)

Contributors:

• @duncan771 (#86)

Full Changelog: v0.8.1...v0.8.2

v0.8.1 dbt_salesforce_formula_utils

Happy Thursday 🦖

Features

• Updated the README for easier use and navigation of the package (PR #78).

Bug Fixes

(PR #77) includes the following changes:

• In v0.8.0, the using_quoted_identifiers argument in the sfdc_formula_view() macro was erroneously removed, making its default value of False immutable. It has been reintroduced.
• using_quoted_identifiers now uses warehouse-specific quoting syntax.

dbt_salesforce_formula_utils v0.8.0

🚨 Breaking Changes 🚨:

PR #64 includes the following breaking changes:

• The default behavior of the sfdc_formula_view macro now has the full_statement_version equal to true. This means, by default the macro will search for the fivetran_formula_model source table (full SQL statement for each object) opposed to the fivetran_formula source table (individual formulas).
  • Please be sure to update your macros that intend to reference the fivetran_formula source table accordingly.
• 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
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

dbt_salesforce_formula_utils v0.7.2

Happy Monday and international horse day 🐴

This release of the dbt_salesforce_formula_utils package includes the following updates:

Features

• Incorporated a new boolean argument (using_quoted_identifiers) to the sfdc_formula_view macro. This argument allows users to quote the compiled sql generated by the macro. This is especially necessary when a users warehouse has case sensitivity enabled. If a user has a warehouse with case sensitivity, they will likely see the macro fail by default. If this is the case, you will want to set the using_quoted_identifiers argument to true (the argument is false by default). (#72)
• Updated documentation within the README for easier understanding of the macros and how to use them in a dbt project. (#70)

Under the Hood

• Added BuildKite integration tests. (#72)
• Added the docs folder for dbt docs hosting on GitHub Pages. (#72)
• Upgraded dbt-expectations dependency within the package integration_tests to the [">=0.8.0", "<0.9.0"] range. (#72)

Contributors

• @fivetran-adamrees (#70)

dbt_salesforce_formula_utils 0.7.1

Happy Tuesday 🌮

This release of the dbt_salesforce_formula_utils package includes the following updates:

Features

• README edits for easier navigation and understanding of how to use the solution. (#61)

Bug Fixes

• The dbt_utils.get_column_values macro for the full_statement_version of the package was not properly filtering for only the relevant source table records within the fivetran_formula_model source table. A where clause has been added to remedy this issue. (#61)

dbt_salesforce_formula_utils 0.7.0

Happy Wednesday! 🐫

This release of the dbt_salesforce_formula_utils package includes the following updates:

Features

• Addition of the full_statement_version argument within the sfdc_formula_view macro. (#55)
  • This argument is a boolean and will allow users to either leverage the default (false) version of the macro to pull individual formulas from the fivetran_formula table to be produced in the materialized view, or (true) leverage the fivetran_formula_model source to generate the entire sql statement that will be materialized in warehouse.