Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] multiple zendesk instances #124

Open
2 of 4 tasks
CaseyLeab opened this issue Nov 8, 2023 · 5 comments
Open
2 of 4 tasks

[Feature] multiple zendesk instances #124

CaseyLeab opened this issue Nov 8, 2023 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@CaseyLeab
Copy link

Is there an existing feature request for this?

  • I have searched the existing issues

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?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

No response

@CaseyLeab CaseyLeab added the enhancement New feature or request label Nov 8, 2023
@fivetran-jamie
Copy link
Contributor

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?

@CaseyLeab
Copy link
Author

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.

@fivetran-jamie
Copy link
Contributor

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?

@CaseyLeab
Copy link
Author

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.

@mariahjrogers
Copy link

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!

@fivetran-jamie fivetran-jamie mentioned this issue Nov 20, 2024
7 tasks
@fivetran-jamie fivetran-jamie added type:duplicate This issue or pull request already exists and removed type:duplicate This issue or pull request already exists labels Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants