Forum Discussion
OData issue using Power BI API
- 6 years ago
Final managed to solve this issue.
I had to delete and re-add the SPNs for the ReportServer Service account. The OData connectivity now works.
Why? Don't know but it works.
he following “brick walls” were encountered:
The PowerBI Zendesk plugin only works if you install the 32-bit version of Power BI desktop client. If you don’t use it, the authentication dialogue box doesn’t work.
No Zendesk plug-in for Excel Power Query.
I am therefore forced to use JSON calls in Power Query for Excel instead and decided to use the same code for PowerBI desktop client. That is, I didn’t use the Zendesk plugin in Power BI.
I now discover that auto refresh of datasets in PowerBI.com does not support the JSON call methods employed.
I now realize that I have no choice to use different queries in PowerBI and Excel. One that uses the Zendesk plugin (PowerBI) and one that uses JSON calls (Excel).
I’m back to using a 32-bit version of Power BI Desktop Client because I’m using the Zendesk plugin. Guess what? It crashes all the time. 32-bit means less memory to play with and with PowerBI modelling, you want as much memory as possible.
It seems that if I load too much data with the timesheet data queries, then PowerBI crashes. In order to publish the PowerBI report, I need to limit the timesheet queries to 2 timesheet periods. However, I want to load almost 4 months’ worth, but more on that later.
My Power Query employs “dynamic variables” to calculate the two most recent reporting periods and these are passed to the $filter query option in the odata query.
I hope this information helps!
Regards,
Lewis
developer
Anonymous did you maybe post this reply to the wrong thread? It looks like your issues related to the ZenDesk connector on the cloud service. This thread is about connecting to the Power BI Report Server API on-prem.