Forum Discussion
DataSource.Error: We couldn't parse OData response result. Error: Unexpected end of file has occurre
- 6 months ago
Hii SueM
It is usually caused by server-side issues such as timeout, large payload size, network interruption, or the OData service crashing while generating the response.
To resolve:
-
Check the OData URL directly in a browser or Postman to confirm it returns a complete response.
-
Reduce the dataset size using $filter, $select, or pagination.
-
Enable server-side paging if supported.
-
Verify there are no gateway, timeout, or proxy limits.
-
If it persists, it must be fixed on the OData service side (not in Power BI).
-
- 6 months ago
Thank you, I think reducing the data set will resolved it.
Hii SueM
It is usually caused by server-side issues such as timeout, large payload size, network interruption, or the OData service crashing while generating the response.
To resolve:
-
Check the OData URL directly in a browser or Postman to confirm it returns a complete response.
-
Reduce the dataset size using $filter, $select, or pagination.
-
Enable server-side paging if supported.
-
Verify there are no gateway, timeout, or proxy limits.
-
If it persists, it must be fixed on the OData service side (not in Power BI).