Detail what changes this PR introduces and how this addresses the issue/feature request linked above.
This PR includes the locations_pass_through_columns in netsuite2__transaction_details table, besides the location_id column. This aligns with the already existing behavior of accounts_pass_through_columns and departments_pass_through_columns.
How did you validate the changes introduced within this PR?
Manual testing in my company setup (changing the file directly in dbt_installed_packages/).
Which warehouse did you use to develop these changes?
Databricks
Did you update the CHANGELOG?
[ ] Yes
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
[ ] Yes
Provide an emoji that best describes your current mood
:sunglasses:
Please provide your name and company Antonio Ruby Barreto, Fastned
Link the issue/feature request which this PR is meant to address https://github.com/fivetran/dbt_netsuite/issues/123
Detail what changes this PR introduces and how this addresses the issue/feature request linked above. This PR includes the
locations_pass_through_columnsinnetsuite2__transaction_detailstable, besides thelocation_idcolumn. This aligns with the already existing behavior ofaccounts_pass_through_columnsanddepartments_pass_through_columns.How did you validate the changes introduced within this PR? Manual testing in my company setup (changing the file directly in dbt_installed_packages/).
Which warehouse did you use to develop these changes? Databricks
Did you update the CHANGELOG?
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
Provide an emoji that best describes your current mood :sunglasses: