v0.7.0 dbt_microsoft_ads

PR #28 includes the following updates:

Breaking changes

• Updated the following identifiers for consistency with the source name and compatibility with the union schema feature:

current	previous
microsoft_ads_account_performance_daily_report_identifier	microsoft_ads_account_daily_report_identifier
microsoft_ads_ad_group_performance_daily_report_identifier	microsoft_ads_ad_group_daily_report_identifier
microsoft_ads_ad_performance_daily_report_identifier	microsoft_ads_ad_daily_report_identifier
microsoft_ads_campaign_performance_daily_report_identifier	microsoft_ads_campaign_daily_report_identifier
microsoft_ads_keyword_performance_daily_report_identifier	microsoft_ads_keyword_daily_report_identifier
microsoft_ads_search_query_performance_daily_report_identifier	microsoft_ads_search_query_daily_report_identifier

• If you are using the previous identifier, be sure to update to the current version!

Feature update 🎉

• Unioning capability! This adds the ability to union source data from multiple microsoft_ads connectors. Refer to the Union Multiple Connectors README section for more details.

Under the hood 🚘

• In the source package, updated tmp models to union source data using the fivetran_utils.union_data macro.
• To distinguish which source each field comes from, added source_relation column in each staging and downstream model and applied the fivetran_utils.source_relation macro.
  • The source_relation column is included in all joins in the transform package.
• Updated tests to account for the new source_relation column.

PR #25 includes the following updates:

• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job.
• Updated the pull request templates.

Full Changelog: v0.6.0...v0.7.0