Merge pull request #88 from fivetran/release/v0.8.2

Release/v0.8.2

CHANGELOG.md

@@ -1,9 +1,15 @@
-# dbt_salesforce_formula_utils v0.UPDATE.UPDATE
+# dbt_salesforce_formula_utils v0.8.2
+## Features
+- Clarify Step 5 of the README that `sfdc_exclude_formulas` works only with Options 2 and 3. ([#88](https://github.com/fivetran/dbt_salesforce_formula_utils/pull/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](https://github.com/fivetran/dbt_salesforce_formula_utils/pull/86))
+- Incorporated the new `fivetran_utils.drop_schemas_automation` macro into the end of each Buildkite integration test job. ([#82](https://github.com/fivetran/dbt_salesforce_formula_utils/pull/82))
+- Updated the pull request [templates](/.github). ([#82](https://github.com/fivetran/dbt_salesforce_formula_utils/pull/82))
 
- ## Under the Hood:
+## Contributors:
+- [@duncan771](https://github.com/duncan771) ([#86](https://github.com/fivetran/dbt_salesforce_formula_utils/pull/86))
 
-- Incorporated the new `fivetran_utils.drop_schemas_automation` macro into the end of each Buildkite integration test job.
-- Updated the pull request [templates](/.github).
 # dbt_salesforce_formula_utils v0.8.1
 
 ## Features

README.md

@@ -114,15 +114,19 @@ source dbt_modules/salesforce_formula_utils/sfdc_formula_model_automation.sh "..
 
 > Note: In order for this command to work, you must currently be within the root directory of your dbt project. 
 
-## Step 5: Exclude problematic formula fields
-The `sfdc_formula_view` macro has been created to support double-nested formula field references for most cases using Option #1, however, never if using Options #2 or #3. For example:
-- :white_check_mark: : A formula field references standard fields from the base Salesforce table.
-- :white_check_mark: : A formula field references another formula field that does **not** reference other formula fields.
+## Step 5: Exclude problematic formula fields (for Option #2 or #3)
+The `sfdc_formula_view` macro supports double-nested formula field references for most cases using Option #1, however, it does not support Options #2 or #3. 
 
-The `sfdc_formula_view` macro may be able to support some cases of n-nested formula field references if using Option #1 above, however, never if using Options #2 or #3. For example:
+For example:
+- ✅ : A formula field references standard fields from the base Salesforce table.
+- ✅ : A formula field references another formula field that does **not** reference other formula fields.
+
+The `sfdc_formula_view` macro may support some cases of n-nested formula field references using Option #1, however, it does not support Options #2 or #3. 
+
+For example:
 - 🚧     : A formula field references another formula field that references another formula field (and so on...). 
 
-If you have a formula field that is double-nested or is otherwise not compiling, exclude it from all your models by setting the `sfdc_exclude_formulas` variable within your root `dbt_project.yml` file. Configure this variable as a set of all the fields you would like to exclude from all models. See below for an example:
+When using Options #2 or #3 with a formula field that is double-nested or is otherwise not compiling, exclude it from all your models by setting the `sfdc_exclude_formulas` variable within your root `dbt_project.yml` file. Configure this variable as a set of all the fields you would like to exclude from all models. This is for Options #2 or #3 only and will *not* work with Option 1. See below for an example:
 ```yml
 vars:
   sfdc_exclude_formulas: ('field_that_references_other_formula','other_triple_ref_field','field_i_just_dont_want')

dbt_project.yml

@@ -1,4 +1,4 @@
 name: 'salesforce_formula_utils'
-version: '0.8.1'
+version: '0.8.2'
 config-version: 2
 require-dbt-version: [">=1.3.0", "<2.0.0"]

integration_tests/dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'salesforce_formula_integration_tests'
-version: '0.8.1'
+version: '0.8.2'
 profile: 'integration_tests'
 config-version: 2
 vars: