Forum Discussion

SueM's avatar
SueM
Helper I
6 months ago
Solved

DataSource.Error: We couldn't parse OData response result. Error: Unexpected end of file has occurre

Hello   We have this message when loading data from OData.  DataSource.Error: We couldn't parse OData response result. Error: Unexpected end of file has occurred. The following elements are not cl...
Need Help
  • rohit1991's avatar
    rohit1991
    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).

  • SueM's avatar
    SueM
    6 months ago

    Thank you, I think reducing the data set will resolved it.

v-menakakota's avatar
v-menakakota
Community Support
6 months ago

Hi SueM ,

Thanks for reaching out to the Microsoft fabric community forum. 

 

I would also take a moment to thank rohit1991   , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .

 

 

Best Regards, 
Community Support Team

v-menakakota's avatar
v-menakakota
Community Support
6 months ago

Hi @SueM ,

Thanks for reaching out to the Microsoft fabric community forum. 

 

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .

 

Best Regards, 
Community Support Team