api updates as of 2/3

[fivetran-sheringuyen]

❗ ❗ We are currently waiting for data to verify the updates before merging and releasing the changes in this PR. If you are currently using our Linkedin Source Package and would like to test out this version of the package, we would love to hear about your experience. Please feel free to comment below and let us know what your experience is!

For those interested, you can test out this version by adding the below in your packages.yml and temporarily comment out your current version of dbt_linkedin_source. Note, if you are using the dbt_linkedin package, please refer to the instructions for that package instead!

packages:
  - git: https://github.com/fivetran/dbt_linkedin_source.git
    revision: feature/linkedin-api-updates-2023
    warn-unpinned: false

❗ ❗ Are you a current Fivetran customer?

Fivetran Employee 💃

What change(s) does this PR introduce?

🚨 Breaking Changes 🚨

Due to Linkedin Ads API change in January 2023, there have been updates in the Linkedin Ads Fivetran Connector and therefore, updates to this Linkedin package.

The following fields have been completely deprecated in the stg_linkedin_ads__creative_history model (PR #48):

• type
• call_to_action_label_type
• version_tag

Updates

• The following legacy fields have been updated respectively in the connector and [PR #48](https://github.com/fivetran/ dbt_linkedin_source/pull/48) includes the below modifications:
  • last_modified_time has been updated to last_modified_at
  • created_time has been updated to created_at
  • status has been updated to intended_status
• src_linkedin.yml have been updated to reflect new definitions for the above updated fields.

Under the Hood

• integration_tests/seeds/linkedin_creative_history_data has been updated to reflect new fields and deprecated fields
• Uniqueness testing in stg_linkedin_ads__creative_history has been updated to now include _fivetran_synced and last_modified_at in place of the previous test with version_tag.

Did you update the CHANGELOG?

• [x] Yes

Does this PR introduce a breaking change?

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

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)

• [x] Yes

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

• [ ] Yes, Issue/Feature [link bug/feature number here]
• [x] No

How did you test the PR changes?

• [x] Buildkite
• [x] Local (please provide additional testing details below)

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

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

Provide an emoji that best describes your current mood

:dancer: **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](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.

[fivetran-sheringuyen]

To-do:

• [x] Docs to be generated before merge & release!