Processing Error: The key didn't match any rows i...

Anonymous · ‎08-02-2017

I created a PowerBI desktop file and uploaded to the online service at app.powerbi.com. The desktop file refreshes just fine, but once it is published to the online service any refreshes fail with:

There was an error when processing the data in the dataset.

Data source type:
Processing error:	The key didn't match any rows in the table.
Cluster URI:	WABI-CANADA-CENTRAL-redirect.analysis.windows.net
Activity ID:	a3328834-5330-4fd5-943a-2509fb9fd7c7
Request ID:	f51bfbd2-8981-4bec-abe9-17d794c22d4d
Time:	2017-08-01 21:14:06Z

I can't get any useful information from this error, and I don't know what to do to dig in further. Other solutions for similar errors point to solutions around refreshing and republishing the desktop file or the connections, but this doesn't work for me. Is there any way to get a better error message?

The data sources in my pbix file come from Zendesk, using the Zendesk(beta) connector from the Get Data list.

Thank you.

Anonymous · ‎08-04-2017

@Anonymous,

The above error could occur when your account that is used to connect to Zendesk data source doesn’t have sufficient permissions.

I would recommend you go to Settings->Datasets and find your dataset in Power BI Service, re-enter credential for the Zendesk data source, and ensure that the credential you entered is same as that you use in Power BI Desktop.

Regards,

Anonymous · ‎08-04-2017

Thank you @Anonymous. I was able to figure more information about what happened. There are a set of tables on Power BI Desktop coming from the Zendesk connector that look like the below snip-- that are 20 of them. When I publish to Power BI Online, there are only 13 available; 7 were dropped somehow. The refresh fails because I reference that one missing table in a query. Can you tell me what I can do, or how I can debug why the connector does not provide the same data online as it does at the Desktop?

The credentials I use are the same on both Power BI Desktop and Online for the refresh.

The table I need that is missing online is ticket_fields.

Anonymous · ‎08-09-2017

@Anonymous,

Could you please create a single report that only contains ticket_fields and data of other missing tables, then publish report to Power BI Service and check if you can refresh this report in Service?

Regards,
Lydia

Anonymous · ‎08-09-2017

Hi @Anonymous

Yes, I did that. I narrowed it down to one table that could not refresh. It could not refresh because the ticket_fields "Key" was not in result from the base Zendesk connector at:

= Zendesk.Tables("https://company.zendesk.com")

The list of tables returned by this command on the desktop is larger than those in the online service. In particular, "ticket_fields" is missing (among others). That list of tables is indexed by a key column, which is "ticket_fields".

We also asked for support fom Zendesk, however they said that this connector is a Microsoft product and could not do anything about it.

Thanks!