Open CaseyLeab opened 1 year ago
hey there! we were actually heavily considering rolling this out in the coming quarter.
i am curious about your use case -- does each zendesk instance belong to a different department or subsidiary in your org?
hey there! we were actually heavily considering rolling this out in the coming quarter.
i am curious about your use case -- does each zendesk instance belong to a different department or subsidiary in your org?
Yes, we have 5 different zendesk instances and each belongs to a different organization in the building and different metrics, tickets, and tracking associated to it. In zendesk they're separated by different subdomains so there is an individual connector for each in Fivetran.
Gotcha! so the solution we were thinking of rolling out would union together these different instances' source data and produce 1 set of output models -- which you could split out into individual ones based on the source_relation
column. would that work for your use case?
I think that would work. Thank you. Please keep me posted when you prioritize and plan to roll this out as our depts are bummed that ticket_metrics is the biggest table they aren't able to see at the moment.
Hi, I was wondering if you could provide an update on the progress of this issue @fivetran-jamie ? I am eager for this to be released!
Is there an existing feature request for this?
Describe the Feature
We have multiple zendesk instances in our organization, how would I setup this package so that I can create the models for each of the zendesk instances we have. (They are all in separate schemas; zendesk_concierge, zendesk, zendesk_partner_success, etc....)
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Anything else?
No response