Forum Discussion
Dynamics 365 OData error with Power BI desktop
Excellent, that got it working. Thanks.
MS support engineer said if you're CRM instance is above 9.0.2.751, it will now include the fix and Power shouldn't have the issue anymore.
Helper ISeveral customers had their appsource start working last week. Definitely a backend problem.
9.0 and 8.2 within your URL source with both work now too
9.0.2.751 also began enforcing 10+ calculated field query limits in powerbi (some other apps have had this limitation for a while now).
We kept having intermittent issues with powerbi the last few months so we made the move to azure sql data export service. Not too hard to do (Have to change your reports a bit or a lot depending on the report/datasets). Azure sql refreshes incredibly faster and offloads the resources from dynamics if you have a lot of powerbi reports/queries like we did.I have updated Dynamics CRM to Version 1710 (9.0.2.1087) and using V9.0 Odata end point.
https://xxx.api.crm.dynamics.com/api/data/v9.0/
I am unable to use my existing tables in the connections to fetch data, it gives error
"Column name not foung in table"
Also while estabishing new connections getting metadata error and error related to more than 10 custom columns in the entity. I have tried using the old endpoint v8.2 but still getting same errors.
