Forum Discussion
Refresh issues in Power BI Service
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.
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
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.
Did it already. Will have to leave, will pick this tomorrow again, manu thanks for the help until now tayloramy
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!
Issue is still there and not solved
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.
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.
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.
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.
