bugfix/transaction_id

[fivetran-joemarkiewicz]

Are you a current Fivetran customer?

Fivetran created PR

What change(s) does this PR introduce?

• Within the v0.5.1 release, the transaction_id field was erroneously removed from the quickbooks__general_ledger model. This field has since been added back.
• Modified the surrogate_key dbt-util macro argument to be a single list instead of individual strings. This was due to a warning error showing in the command line.

Did you update the CHANGELOG?

• Yes

Does this PR introduce a breaking change?

• Yes (please provide breaking change details below.)
• No (please provide an explanation as to how the change is non-breaking below.)

This PR only adds a field that was erroneously removed in the previous patch release. Adding it back in will not cause breaking changes for users.

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

Is this PR in response to a previously created Bug or Feature Request

• Yes, Issue/Feature [Bug] transaction_id was removed in previous release. #45
• No

How did you test the PR changes?

• CircleCi
• Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

• BigQuery
• Redshift
• Snowflake
• Postgres
• Databricks
• Other (provide details below)

Provide an emoji that best describes your current mood

🆔

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

[fivetran-catfritz]

Successfully ran and tested locally, and changes look good.