Comments (7)
Hi @jordstew thanks for opening this Question! I am sorry to hear you have run into an error on the zendesk__ticket_backlog
model.
This package is intended to run without variable configuration (apart from possibly disabling models if you do not have the table), which is strange to see you are running into an error like this. I just tested this quickly on my end to ensure my models would succeed without variable config and it succeeded with a full refresh run. Have you tried running your package with dbt run --full-refresh
as this may do the trick?
from dbt_zendesk.
Hey @fivetran-joemarkiewicz , that does not work, still same error:
Completed with 1 error and 0 warnings:
Database Error in model zendesk__ticket_backlog (models/zendesk__ticket_backlog.sql)
000904 (42000): SQL compilation error: error line 644 at position 35
invalid identifier 'TICKET_FIELD_HISTORY.ASSIGNEE_ID'
compiled SQL at target/run/zendesk/models/zendesk__ticket_backlog.sql
When I look at the compiled code, like I described in my first post, it is clear why this is erroring and not working. I have no custom variables in my dbt_project.yml file besides this:
vars:
zendesk_schema: ZENDESK_SUPPORT_SECURE
zendesk_database: RAW
zendesk_source:
using_schedules: false
group: "{{ source('zendesk', 'group_') }}" # Disable if you do not have the schedule and ticket_schedule tables, or if you do not want metrics reported in business hours # Disable if you are not using SLAs
zendesk:
using_schedules: false
reason for the group in the zendesk_source variable is because we have to recreate it as GROUP_ because group is a reserved word in snowflake and it does not work when have a table simply named group, as it thinks we are doing a group by.
Any other ideas, Joe?
from dbt_zendesk.
Hmm my variable config looks very similar to yours, but I am unable to replicate the error. Would you be able to clarify which version of the package you are using?
Looking at your past comments I noticed the models are CTE's, whereas for me they are materializing as tables. I also see your error line for the backlog model is at line 644, while my backlog model target only contains ~70 lines?
from dbt_zendesk.
Would it help if I sent you the compiled query for reference? I am using version 0.4.1
from dbt_zendesk.
As it seems the compiled query is extremely long, I feel it would probably be best if we would be able to debug this live.
You can schedule some time to chat with myself and members of our team on our Calendly link for Thursday so we can debug live and hopefully get the package running successfully for you! Let me know if you have any questions.
from dbt_zendesk.
Hey Joe I figured it out. So for the first version of zendesk hub and zendesk source hub, we did the following in our dbt_project.yml:
zendesk:
#+database: EDW
#+schema: ZENDESK_SECURE
+database: DE_SANDBOX
+schema: JSTEW
+materialized: ephemeral
zendesk_sla_breach:
+materialized: table
zendesk_ticket_enriched:
+materialized: table
zendesk_ticket_field_history:
+materialized: table
zendesk_ticket_metrics:
+materialized: table
zendesk__ticket_summary:
+materialized: table
zendesk__ticket_backlog:
+materialized: table
zendesk_source:
#+database: EDW
#+schema: ZENDESK_STG_SECURE
+database: DE_SANDBOX
+schema: JSTEW
+materialized: table
we did this because we want the models to be materialized as tables instead of views. this worked for the first version of the zendesk hub, but now having this line about all other materializations being ephemeral seemed to break it:
zendesk:
#+database: EDW
#+schema: ZENDESK_SECURE
+database: DE_SANDBOX
+schema: JSTEW
**+materialized: ephemeral**
having this works:
zendesk:
#+database: EDW
#+schema: ZENDESK_SECURE
+database: DE_SANDBOX
+schema: JSTEW
#+materialized: ephemeral
zendesk_sla_breach:
+materialized: table
zendesk_ticket_enriched:
+materialized: table
zendesk_ticket_field_history:
+materialized: table
zendesk_ticket_metrics:
+materialized: table
zendesk__ticket_summary:
+materialized: table
zendesk__ticket_backlog:
+materialized: table
Thanks for the help, Joe. You can close this and cancel our working session, and I will also decline it.
from dbt_zendesk.
That's great to hear you were able to get the package to work with the materialization update to the some of those intermediate models.
That also explains the large compile code length. Thanks again for opening this issue and for letting us know you were able to come to a resolution, as such I will close this issue.
from dbt_zendesk.
Related Issues (20)
- [Bug] <Missing business minutes metrics in zendesk support ticket metrics> HOT 29
- [Feature] add passthrough columns for USER and ORGANIZATION
- [Feature] multiple zendesk instances HOT 5
- [Bug] Metrics for "Zendesk Messaging" tickets are incorrect HOT 3
- [Feature] Update dbt_date version requirements to include wider range HOT 2
- [Bug] Zendesk SLAs not accurately being captured for certain First Reply Time Business SLAs HOT 2
- [Bug] Minutes in sla_policies can be inaccurate due to where rounding occurs HOT 1
- [Feature] Support for Zendesk Messaging Chat Channels
- [Feature] Support `periodic_update_time` SLAs
- [Feature] Update Zendesk references in README to Zendesk Support HOT 1
- zendesk fivetran DBT package is incorrectly calculating values from the source data HOT 7
- [BUG] Display correct SLA Breach Time in the `zendesk__sla_policies` model for first and next reply times HOT 1
- [Bug] sla policy events failing due to duplicate values HOT 27
- [Feature] Add Flag for CreatedSolvedClosedSameDay HOT 2
- [Feature] Add Streamlit App documentation to README HOT 1
- [Feature] Incorporate new USER and ORGANIZATION passthrough columns
- int_zendesk__reply_time_business_hours does not run after dbt Package update HOT 5
- [Bug] Not able to disable package model of dbt_packages/zendesk_source/models/tmp/ HOT 2
- [Bug] Agent Work Time and Requester Wait Time Erroneously Being Filtered Out of zendesk__sla_policies
- [Feature] Incoprorate Historical Schedule Changes
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dbt_zendesk.