v1.5.0-a1 dbt_intercom
Pre-release
Pre-release
·
2 commits
to bugfix/assignee_type_deprecation
since this release
PR #75 includes the following updates:
Schema/Data Change
3 total changes • 2 possible breaking change
| Data Model(s) | Change type | Old | New | Notes |
|---|---|---|---|---|
intercom__conversation_enhancedintercom__conversation_metrics |
New field | conversation_assignee_id |
Exposes the conversation assignee ID (the ID of the user assigned to the conversation) from the staging layer for reference and joins. If you persist assignee_id via the intercom__conversation_history_pass_through_columns variable, ensure its alias does not match conversation_assignee_id to avoid duplicate column errors |
|
intercom__conversation_enhancedintercom__conversation_metrics |
New field | is_assignee_admin |
Boolean field indicating whether the conversation assignee is an admin user, determined by joining assignee_id with the admin table. Returns false if conversation is unassigned or assigned to a non-admin user |
|
intercom__conversation_enhancedintercom__conversation_metricsstg_intercom__conversation_history |
Deprecated field | assignee_type or conversation_assignee_type |
Marked as [DEPRECATED] | The assignee_type field is no longer supported by Intercom's API. Use is_assignee_admin instead to determine if an assignee is an admin |
Under the Hood
- Updated
intercom__admin_metricsto filter conversations usingis_assignee_adminboolean instead of the deprecatedconversation_assignee_type = 'admin'string comparison - Enhanced
intercom__conversation_enhancedwith a left join to the admin table to determine admin assignee status - Updates to the integrity and consistency validation tests to ensure accurate testing of model changes between versions.
Full Changelog: v1.4.0...v1.5.0-a1