Recent searches


No recent searches

Using the Power BI Connector by Zendesk (Beta)



Edited Feb 07, 2025


-1

40

40 comments

Hi Scott Tynan , the search api only supports Offset Based Pagination, alternatively, you can use the Export Search Results api which supports Cursor Based Pagination. 
Example: /api/v2/search/export?filter[type]=ticket&page[size]=1000&query=created>2024-01-01 created<2024-01-31
This will return tickets, including archived ones, for January 2024, with pagination. You can adjust the number of records to 1000 per page, although Zendesk recommends sticking to 100 records per page to avoid performance issues.

This article explains how to query data using cursor pagination. 

 

0


Hello team,

Could you help me understand how to establish a relationship between the Tickets table and the Organization table?

1


Lucas Neves Silva  Tickets > Requester > Organization

0


I have successfully connected to Zendesk with Power BI using the Beta connector. However,
1. I can't locate any of our model numbers, and without them, the data is incomplete and unusable. I created a ticket about this but no luck. Please help 
2. How do get the older data? with the Beta connector can only access recent tickets.

3. why it takes hours to refresh? is there a way to tune it?

1


Is there a way to set up incremental refresh in Power BI dataflows using the new connector? Loading all data takes too much time and is not efficient. I've tried filtering on the updated_at and created_at fields in the ticket table, but it seems like the filter is not query folding back to the source.

 

If I understand correctly, the connector will only allow us to fetch the last 120 days of tickets, since it does not include archived tickets. This greatly reduces the value, since we need to see data and trends over a longer time span.

3


This would be a great feature to support!

 

0


Is there a way to filter the Ticket Data as it is coming in, rather than having to filter it after? 

In the query editor I can use M code to slice it any way I want, however, the first step always brings in the full Tickets table. My organization has a large amount of tickets, so when I try to bring in that table, it just breaks as there is too much data.

When pulling data from various SQL databases there is usually an option to pull in the data with a query, meaning I can just pull in the rows and columns I want from the get go. This is essential as I can limit the amount of data I am pulling in on the first step and it will actually load. Is there any way to do something similar with this connector? 

Without the ability to pull old tickets as other commentors have mentioned and without the ability to filter data on retrieve, this connector is pretty much worthless for most business scenarios. Like why even bother making this thing at all

 

 

5


Operations Specialist :
Unfortunately the connector does not support query folding. I contacted Zendesk Support and they confirmed this. So the connector will load all data, then filter it after it reaches Power BI. This makes the connector not usable if you have large ticket volumes, since the refresh will eventually time out.  The fact that it will only let you pull the last 120 days of tickets, was also a showstopper for us.

I ended up using the CData Zendesk connector for Power BI, and this works great. It does require that you have a Power BI gateway set up to allow for refresh in Power BI service. The CData connector supports incremental refresh / query folding on the created_at and updated_at fields, and it allows you to load all historical data. I was able to load all +1 million tickets dating back to 2019.

The alternative would be to use the Zendesk API directly in Power BI, but this requires quite a bit of effort to set up and maintain.

1


Hi which end point has the time logged data?

 

 

Thanks. 

0


Hi 

 

Which end point has the time recorded data?

 

Thanks. 

0


Please sign in to leave a comment.