OData refresh fails in Power BI Service but works in Desktop

[benjos23]

Hi everyone,

I’m facing a frustrating issue with OData refresh in Power BI Service. I’m pulling data from an ERP (Business Central) using OData feeds, and I have a Power BI report that works fine in Desktop. However, when I publish it and refresh in Power BI Service, it fails for some datasets but works fine for others.

The ERP manages multiple companies, and each company has its own OData endpoint. The data structure is exactly the same for all of them, only the company identifier in the URL changes. To handle this dynamically, I use a parameter in Power BI that modifies the OData URL based on the selected company.

The strange part is that, for some companies, the dataset refresh successfully in Power BI Service, while for others it fails after a few minutes with this error:

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError",
"pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError",
"parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode",
"detail":{"type":1,"value":"-2147467259"}},
{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage",
"detail":{"type":1,"value":"OData : Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."}},
{"code":"DM_ErrorDetailNameCode_UnderlyingHResult",
"detail":{"type":1,"value":"-2147467259"}},
{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind",
"detail":{"type":1,"value":"OData"}},
{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath",
"detail":{"type":1,"value":"http://erp/prod/ODataV4/Company('CompanyB')/DimensionValue"}},
{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],
"exceptionCulprit":1}}}

Everything works fine in Power BI Desktop for all companies. I also tested the failing OData URLs in a browser and Postman, and they return data correctly.

Some key points:

• The Power BI Gateway is online and properly configured.
• Same authentication settings for all companies.
• The table in the error (DimensionValue) only returns 1000 rows
• Refreshing one company at a time doesn’t change anything – the same ones always fail.

At this point, I’m stuck. Could this be a Power BI Service timeout issue? Would it be my Power Query ETL pipeline that takes too long ? If anyone has insights, I’d really appreciate your help!

Thanks in advance!

PS : this issue was generated with help of an LLM.

[benjos23 · Accepted solution]

Hi @v-menakakota,
The problem I described appeared suddenly, it was not a problem of how Power BI Service was resolving the parameter. 
What I did was changing some of my queries in Power Query, simplifying them and make them lighter, I guess. I don't really know what changed exactly, maybe my semantic model was too big ? It's a shame that the errors are not descriptive enough ... 
Anyway, at least it works now.
Thank you for your help though.

[v-menakakota]

Hi @benjos23 ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-menakakota]

Hi @benjos23 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-menakakota]

Hi @benjos23 ,

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

Since you're using a parameter to modify the OData URL dynamically based on the selected company, have you double-checked that the parameter is resolving correctly in Power BI Service
Go to Dataset settings then Parameters and make sure the expected values are being passed in the Service. Sometimes, default values behave differently in Desktop vs. Service.
Instead of using the parameter, manually enter the failing company's URL in Power Query and test if it refreshes in the Service. If it works, the issue could be with how the parameter is being applied.

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.