Forum Discussion
Processing Error: The key didn't match any rows in the table.
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,
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
- Anonymous9 years agoNot applicable
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!
- Anonymous9 years agoNot applicable
Anonymous,
I would recommend you open a support ticket on the support.powerbi.com site.
Regards,