Forum Discussion
Dynamics 365 OData error with Power BI desktop
Excellent, that got it working. Thanks.
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.
My organisation updated to V9.0 (9.0.2.1087) over the weekend, in order to get my reports working again I tried simply editing the "v8.2" to 9.0 in the URL.
This didn't work despite the URL being as detailed from the Developer Resources page:
To confirm the correct source required, I chose to create a new query using the Dynamics 365 Connector.
After choosing a random table, I checked the query in advanced editor and found the code had added two extra statements after the url, in addition to updating to "v9.0":
I changed my existing queries to this and now everything is functioning correctly.
I would suggest creating your own new query to check the correct information is being generated rather than assuming what works for me will work for you.
Hope this is helpful to someone.