Error when i tried to refresh ADOTesPoints OData in Dataflow, works fine in PowerBI Desktop M Query,

Am trying to pull data from ADO Testpoints OData which is created in Dataflow. same query works fine in PowerBI Desktop let Source = OData.Feed("https://analytics.dev.azure.com/MyOrg/MyProj/_...

General Comment

Need Help

Show and Tell

Tips and Tricks

v-aatheeque
8 months ago
Hi sravs2007

Yes, staging OData data into a database and connecting Power BI to the DB is a recommended best practice. It avoids OData service limitation and typically results in more stable refresh and better performance.

Reference : https://learn.microsoft.com/en-us/power-query/connectors/odata-feed

Hope this helps!!
Thank You.

v-aatheeque

Community Support

8 months ago

Hi sravs2007

Thanks for raising this query in Microsoft Fabric Community Forum.
A 500 (Internal Server Error) from an OData source means the service failed to process the request. This is usually caused by a temporary service issue, an invalid/unsupported query, or limitations on the source side when Power BI pushes down the query.

Confirm that the OData connector is supported for Dataflows in your workspace. Some connectors work in Power BI Desktop but have limitations in the Service.
If the OData source uses Microsoft Entra ID (OAuth), the refresh token may expire during Service refresh. Re‑authenticate the dataflow and verify credentials in the Service.
Double‑check your query logic for discrepancies compared to what works in Desktop. Ensure all columns being pulled are correctly defined in the query.
Ensure the on‑premises data gateway is online, correctly mapped, and updated to the latest supported version. Verify the dataflow is correctly bound to the gateway.
Large payloads or complex OData queries can fail in the Service due to timeouts or resource limits. Try reducing the data volume (filters/date range) to test if this is a size or timeout issue.
Paste the OData URL into a browser to confirm the service itself responds correctly. If it fails there, the issue is server‑side.

Reference : Troubleshoot refresh scenarios - Power BI | Microsoft Learn

Hope this helps !!

Thank You.