Refresh issues in Power BI Service

[Orlando_Tuga]

In Power BI Desktop i have a report that when i refresh is ok and all is good and data is fine. I published it and when i refresh the data in Power BI i get an error as following:

Error fetching data for this visual

The query referenced calculated column '<oii>Market Place Price Input</oii>'[<oii>New_Part_Check</oii>] which does not hold any data because evaluation of one of the rows caused an error.

Please check the technical details for more information. If you contact support, please provide these details.Hide details

• Underlying ErrorQueryUserError
• Activity ID8cae7b62-e5d2-485d-b715-36e9624349d0
• Correlation ID4a9406f8-a2a4-5d5a-e709-bcf6c7a1f223
• Request IDc9b49833-c3f5-4857-9799-aa00a01dac4a
• TimeThu Sep 11 2025 18:10:14 GMT+0100 (Western European Summer Time)
• Service version13.0.26598.35
• Client version2508.4.25849-train
• Cluster URIhttps://wabi-japan-east-redirect.analysis.windows.net/

  Can you help me understand what is the issue please? 

[tayloramy · Accepted solution]

Hi @Orlando_Tuga, 

So far we confirmed that the data at source is valid, and that the crednetials are valid. There's no gateway to cause problems in the middle, and the sharepoint connection is properly referencing the web source and not a local copy of the file. 

I'm not sure why PowerQuery is returning rows with errors in the service but not in desktop.  

@v-tejrama do you have any suggestions? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution.

[PBI_Consultant · Accepted solution]

Hi @Orlando_Tuga,
This means that the calculated column New_Part_Check in the table Market Place Price Input is failing to evaluate for at least one row when refreshed in the Power BI Service. It will work in Desktop but it will throw an error in service, both work differently. So, first you enter at least one row in the table and then try to refresh it.
Thanks

[tayloramy · Accepted solution]

Hi @Orlando_Tuga, 

So far we confirmed that the data at source is valid, and that the crednetials are valid. There's no gateway to cause problems in the middle, and the sharepoint connection is properly referencing the web source and not a local copy of the file. 

I'm not sure why PowerQuery is returning rows with errors in the service but not in desktop.  

@v-tejrama do you have any suggestions? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution.

[tayloramy]

Hi @Orlando_Tuga, 

This is saying that one of the M queries had an error, resulting in no data for that column, which is then referenced later on. 

Are you able to do a full refresh in desktop, not just the preview? 

If so, can you identify what query this column is coming from: <oii>Market Place Price Input</oii>'[<oii>New_Part_Check</oii>]
and let us know what the data source is? 

Last question, are you using an on prem data gateway for this, and are the connections set up properly in there if so? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution.

[Orlando_Tuga]

Hi @tayloramy  answering your questions:

1) I can do a full refresh on Desktop without any errors

2)The Table 'Market Place Price Input' source is an excel file in Share point and 'New Part Check' is a text calculated column that gives no errors in desktop

3)Have no gateway configured or active it's through Cloud connections and all credentials are ok

Very strange and never happened to me

[tayloramy]

Hi @Orlando_Tuga, 

That helps a lot. Where is the excel file located? 
Can you send a screenshot of what the advanced editor of the query for the excel file looks like in desktop? 

Thanks, 

Taylor. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution. 

[Orlando_Tuga]

The Calculated Column type Text

[Orlando_Tuga]

[tayloramy]

Hi @Orlando_Tuga, 

Okay, everything there looks good, that is properly pointing to the web address and not doing anything with local files and onedrive. 

Can you share a screenshot of the data sources page in the semantic properties in the power bi service? We can verify what the connection looks like there.  

Another thought, are there any rows in that sheet that are blank? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution.

[Orlando_Tuga]

No blank rows in the table

[tayloramy]

Hi @Orlando_Tuga, 

Are you able to edit the credentials for all connections just to confirm and be extra sure they are correct? 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, please mark this as the solution. 

[Orlando_Tuga]

Did it already. Will have to leave, will pick this tomorrow again, manu thanks for the help until now @tayloramy 

[v-tejrama]

Hi  @Orlando_Tuga ,

Thank you @tayloramy   for the response provided! 

Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

Thank you for your understanding!

[Orlando_Tuga]

Issue is still there and not solved

[v-tejrama]

Hi @Orlando_Tuga ,

It sounds like the refresh failures you’re running into in the Power BI Service may be connected to the way your calculated column is defined, particularly since it involves nested IF statements along with LOOKUPVALUE. Calculated columns are processed during dataset load, and when they contain complex logic or reference fields with a large number of distinct values, they can create performance issues that sometimes lead to refresh failures in the Service. Problems can also occur if the calculated column depends on tables using DirectQuery or a live connection, as these scenarios aren’t supported. On top of that, calculated columns increase the overall size of the dataset, which in some cases can push the model closer to its capacity limits.

A more reliable approach would be to move this type of logic into Power Query, where the transformations are handled before loading into the model, which reduces the refresh overhead. If the logic is primarily for reporting, you might find that a measure works better, since measures calculate at query time and don’t add to the dataset size. It’s also a good idea to make sure your data source credentials are up to date and that the correct gateway is configured if you’re working with an on-premises source. Reviewing the dataset for optimizations, such as removing unused columns, disabling Auto Date/Time, or enabling incremental refresh for larger models, can also help improve refresh stability and performance.

Implementing these recommendations should help improve refresh stability in Power BI Service.

Best regards,

Tejaswi rama.

[v-tejrama]

Hi  @Orlando_Tuga ,

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you,

Tejaswi.

[v-tejrama]

Hi  @Orlando_Tuga ,

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.

Thank you.

[v-tejrama]

Hi  @Orlando_Tuga ,

I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.

Thank you.