Recent searches


No recent searches

Jin Huang's Avatar

Jin Huang

Joined Feb 05, 2024

·

Last activity Oct 04, 2024

Following

0

Followers

0

Total activity

9

Votes

0

Subscription

1

ACTIVITY OVERVIEW

Latest activity by Jin Huang

Jin Huang commented,

CommentMore integrations

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. 

 

View comment · Posted Oct 04, 2024 · Jin Huang

0

Followers

0

Votes

0

Comments


Jin Huang commented,

CommentMore integrations

Hi Scott Tynan

 

The Search api can return the archived tickets, but the current version of Power BI connector doesn't use this search api. 

 

Regards

Jin

View comment · Posted Sep 20, 2024 · Jin Huang

0

Followers

1

Vote

0

Comments


Jin Huang commented,

CommentMore integrations

Hi Laura Maria Sampedro Hernandez

 

The Power BI connector is using the list tickets api to pull tickets, this api doesn't retrieve archived tickets, that's the reason it appears like data loss. 

 

Regards

Jin

View comment · Posted Sep 19, 2024 · Jin Huang

0

Followers

2

Votes

0

Comments


Jin Huang commented,

CommentMore integrations

Hi Scott Tynan

 

Apologise for the late reply, we did contact Microsoft and report the issue, but they couldn't find the issue in their end.  We tried to reproduce the issue in our end, but it's not reproducible for newly build report. I think the issue is only for old report that was build using the old PowerBI connector, for that case, the only option might be to rebuild the report using the new PowerBI connector. 

 

For future queries, please create a ticket instead of reply in this thread, tickets are more actively monitored and responded. Thank you. 

 

Kind Regards

Jin

View comment · Posted Sep 18, 2024 · Jin Huang

0

Followers

0

Votes

0

Comments


Jin Huang commented,

CommentMore integrations

Regarding the question of why Power BI is returning tickets than it should be, the Power BI connector is using the tickets api  which doesn't include the archived tickets, that's why the tickets numbers might look like they are less than the total count from Support system. 

View comment · Posted Aug 01, 2024 · Jin Huang

0

Followers

1

Vote

0

Comments


Jin Huang commented,

CommentMore integrations

Hi Micky, 

 

There is brand_id field which is the id of the brand this ticket is associated with.

View comment · Posted Aug 01, 2024 · Jin Huang

0

Followers

0

Votes

0

Comments


Jin Huang commented,

CommentMore integrations

Since 10th April, the new Zendesk Power BI connector have been rolled out in Microsoft's April Power BI release. Please download the latest Power BI Desktop from Microsoft for version April 2024 Update (2.128.751.0).

 

View comment · Edited Apr 19, 2024 · Jin Huang

0

Followers

1

Vote

0

Comments


Jin Huang created an article,

ArticleUsing apps and integrations
Disclaimer: Zendesk doesn't provide support for Power BI. See the Microsoft documentation if you need assistance. 

Power BI by Microsoft is a collection of software services, apps, and connectors that work together to turn your unrelated sources of data into interactive insights. Using the Power BI Connector by Zendesk allows you to import your Zendesk data to Power BI. 

This article covers the following topics:

Related articles:

Overview of the Power BI Connector by Zendesk

The existing Zendesk Power BI connector by Microsoft has a known issue where it can’t retrieve records for more than 1000 rows. For example, if an account has more than 1000 tickets, it returns the following 422 error:

Zendesk has developed a new Power BI connector that solves this issue and is currently in beta. The new connector uses Cursor Based Pagination (CBP) to retrieve data from the Zendesk API.

The new connector is named Zendesk Data (Beta). It will eventually replace the legacy connector, which is named Zendesk (Beta Legacy).

BetaLegacy.jpeg

Signing in

The sign in experience is the same as the legacy connector. 

After you sign in, you’ll see all existing endpoints are available in the new connector.

Using the Power Query M language to query data

Disclaimer: Zendesk doesn't provide support for the Power Query M language. See the Microsoft documentation if you need assistance. 

If you are using the Power Query M language to query data, there’s a slight difference in the beginning part of the query. The legacy connector uses Zendesk.Tables() to initialize the Source:

let
   Source = Zendesk.Tables("https://yoursubdomain.zendesk.com"),
   views = Source{[Key="tickets"]}[Data]
in
    views

The new connector uses ZendeskData.Contents() to initialize the Source:

let
    Source = ZendeskData.Contents("https://yoursubdomain.zendesk.com", []),
    Users = Source{[Name="Users"]}[Data]
in
    Users

If you have existing queries using the legacy connector, change the Source initialization part and the rest of the code will work properly. 

If you are using the Power BI connector in any other way, please contact Zendesk Customer Support, and we will provide a migration path. 

 

Edited Feb 07, 2025 · Jin Huang

1

Follower

25

Votes

40

Comments