v0.17.0-a1 dbt_zendesk_source

PR #68 includes the following update:

• Renamed the enablement variable from using_schedule_histories to using_audit_log in stg_zendesk__audit_log to support its expanded use for both schedule and user role histories. Use using_schedule_histories and using_user_role_histories to control downstream model inclusion.

v0.16.0 dbt_zendesk_source

This release includes the following updates from pre-releases v0.16.0-a1 and v0.16.0-a2.

Schema Updates

4 total changes • 0 possible breaking changes

Data Model	Change type	Old name	New name	Notes
stg_zendesk__ticket_chat	New Model			Uses ticket_chat source table
stg_zendesk__ticket_chat_tmp	New Temp Model			Uses ticket_chat source table
stg_zendesk__ticket_chat_event	New Model			Uses ticket_chat_event source table
stg_zendesk__ticket_chat_event_tmp	New Temp Model			Uses ticket_chat_event source table

Feature Updates

• Incorporated the ticket_chat and ticket_chat_event source tables to capture tickets created via chat and native_messaging channels in downstream SLA policy transformations. (PR #63)
• Handled actor_id in ticket_chat_event having inconsistent formatting, so that we can safely cast it as a bigint. Typically, actor_id just contains the ID, but it may also look like agent:<#######>. (PR #63)
• Added the using_ticket_chat variable to enable/disable the ticket_chat and ticket_chat_event staging models and downstream transformations. (PR #63)
  • For Fivetran Quickstart users, using_ticket_chat is dynamically set based on the presence of the ticket_chat and ticket_chat_event source tables.
  • For other users, using_ticket_chat is set to False by default. To change this and enable the ticket chat models, add the following configuration (see README for details).

vars:
  using_ticket_chat: True

Documentation

• Corrected references to connectors and connections in the README. (#PR 61)
• Corrected DAG link in the README. (PR #62)

Contributors

• @segoldma (PR #62)

Full Changelog: v0.15.0...v0.16.0

v0.16.0-a2 dbt_zendesk_source

Bug Fixes

• Handles actor_id in ticket_chat_event having inconsistent formatting, so that we can safely cast it as a bigint. Typically, actor_id just contains the ID, but it may also look like agent:<#######>. (PR #63)

v0.16.0-a1 dbt_zendesk_source

New Features

• Incorporated the ticket_chat and ticket_chat_event source tables to capture tickets created via chat and native_messaging channels in downstream SLA policy transformations. (PR #63)
• Added the using_ticket_chat variable to enable/disable the ticket_chat and ticket_chat_event staging models and downstream transformations. (PR #63)
  • For Fivetran Quickstart users, using_ticket_chat is dynamically set based on the presence of the ticket_chat and ticket_chat_event source tables.
  • For other users, using_ticket_chat is set to False by default. To change this and enable the ticket chat models, add the following configuration (see README for details).

vars:
  zendesk_source:
    using_ticket_chat: True
  zendesk: # if using Zendesk transformation package
    using_ticket_chat: True

Note: If using_ticket_chat is enabled, this update increases the model count of the package by 4 models.

Documentation

• Corrected references to connectors and connections in the README. (#PR 61)
• Corrected DAG link in the README. (PR #62)

Contributors

• @segoldma (PR #62)

v0.15.0 dbt_zendesk_source

Under the Hood

• (Affects Redshift only) Updates the union_zendesk_connections macro to use a limit 1 instead of limit 0 for empty tables.
  • When a table is empty, Redshift ignores explicit data casts and will materialize every column as a varchar. Redshift users may experience errors in downstream transformations as a consequence.
  • For each staging model, if the source table is not found, the package will create a empty table with 0 rows for non-Redshift warehouses and a table with 1 all-null row for Redshift destinations. The 1 row will ensure that Redshift will respect the package's datatype casts.

Documentation Update

• Moved badges at top of the README below the H1 header to be consistent with popular README formats.

Full Changelog: v0.14.2...v0.15.0

v0.14.2 dbt_zendesk_source

PR #59 includes the following updates:

New Features

• Introduced new config variables for whether brand or organization tables are present, allowing customers to either enable or disable the respective staging and tmp models:
  • Updated stg_zendesk__brand (and upstream tmp model) with the new using_brands config variable.
  • Updated stg_zendesk__organization (and upstream tmp model) with the new using_organizations config variable.
  • Updated stg_zendesk__organization_tag (and upstream tmp model) with the new using_organizations config variable, as the organization_tag source table can be disabled in some situations, while organization is not. Thus anything that is disabled/enabled by using_organization_tags should contain both the using_organization_tags AND using_organizations variables.

Under the Hood

• Updated our Buildkite model run script to ensure we test for when using_brands and using_organizations is set to either true or false.

Documentation Updates

• Added enabled config variables to brand, organization and organization_tag in the src_zendesk.yml models.
• Updated README with instructions on how to disable brand and organization sources.

Full Changelog: v0.14.1...v0.14.2

v0.14.1 dbt_zendesk_source

PR #58 includes the following update:

Bug Fixes

• In v0.14.0 (or v0.19.0 of the transform package), Snowflake users may have seen when searching for a relation, dbt found an approximate match errors when running the stg_zendesk__group_tmp model. The issue stemmed from the adapter.get_relation() logic within the union_zendesk_connections macro, which has now been updated to resolve the error.

Full Changelog: v0.14.0...v0.14.1

v0.14.0 dbt_zendesk_source

PR #44 includes the following updates:

Feature Update: Run Package on Unioned Connectors

• This release supports running the package on multiple Zendesk sources at once! See the README for details on how to leverage this feature.

Please note: This is a Breaking Change in that we have a added a new field, source_relation, that points to the source connector from which the record originated.

Documentation

• Added missing documentation for staging model columns.

Full Changelog: v0.13.0...v0.14.0

v0.13.0 dbt_zendesk_source

PR #55 includes the following updates:

Breaking Changes

• Introduced the stg_zendesk__audit_log table for capturing schedule changes from Zendesk's audit log.
  • This model is disabled by default, to enable it set variable using_schedule_histories to true in your dbt_project.yml.
  • While currently used for schedule tracking, this table has possible future applications, such as tracking user changes.

Features

• Updated the stg_zendesk__schedule_holidays model to allow users to disable holiday processing (while still using schedules) by setting using_holidays to false.
• Added field-level documentation for the stg_zendesk__audit_log table.

Under the Hood Improvements

• Added seed data for audit_log to enhance integration testing capabilities.

Full Changelog: v0.12.0...v0.13.0

v0.12.0 dbt_zendesk_source

PR #53 includes the following updates:

Breaking changes

• Added field _fivetran_deleted to the following models for use downstream:
  • stg_zendesk__ticket
  • stg_zendesk__ticket_comment
  • stg_zendesk__user
  • If you have already added _fivetran_deleted as a passthrough columns using the zendesk__ticket_passthrough_columns or zendesk__user_passthrough_columns vars, you will need to remove or alias this field from the variable to avoid duplicate column errors.

Documentation

• Updated documentation to include _fivetran_deleted.

Full Changelog: v0.11.2...v0.12.0