references other queries or steps, so it may not directly access a data source. Please rebuild this

[qmestu]

I've sorted through most of the solutions presented on this board for this kind of error. I'm also using a single .pbix file that does not present this error if i load it on the desktop, but using the service (app.powerbi.com) the error presents itselft. 

My data is 3 tables that are merged, one of them comes from my onedrive, an the other two are from a webservice mall.

I've also isolated these 3 tables in a single file and the error still presents itself.

[lbendlin · Accepted solution]

That's not merge, that's append.

[Poojara_D12 · Accepted solution]

Hi @qmestu 

The issue you're experiencing, where your Power BI report works fine in Power BI Desktop but fails during scheduled refreshes in the Power BI Service, suggests that the root cause is likely related to how Power BI Service handles data source authentication, credentials, or connectivity. Since your data is coming from a mix of OneDrive and a web service, it's important to verify the credentials and permissions for both data sources within the Power BI Service. While the OneDrive connection might work in Power BI Desktop, the Power BI Service may require explicit reauthentication of the OneDrive credentials to ensure that the connection remains valid during scheduled refreshes. Similarly, the web service connection, which often involves API keys, OAuth, or other authentication methods, must be configured correctly in Power BI Service. If there are issues with expired tokens, revoked keys, or incorrect permissions, this could lead to the error you're seeing. To troubleshoot, you should check the data source credentials in the Power BI Service settings and confirm that they are correct and up to date. It’s also important to isolate the problem by testing the refresh for each data source individually—this will help identify whether the issue lies with OneDrive, the web service, or the merging of tables. Additionally, checking the refresh history for detailed error logs can offer insights into what specifically is causing the failure. If the data source credentials appear to be fine, the problem might also be related to the way the tables are merged, as the Power BI Service might struggle with refreshing complex queries that involve multiple data sources. In this case, simplifying the queries or checking for circular references or timeouts could help pinpoint the issue. Lastly, ensuring that any necessary data gateways or service principals are configured correctly in the Power BI Service is essential, as these components may also impact the refresh process. By systematically isolating and testing each data source and connection, you can narrow down the cause of the error and resolve the issue with scheduled refreshes.

[v-prasare]

Hi @qmestu,

Thanks for reaching out MS Fabric community support.

@lbendlin, thanks for your promt response here.

As we haven’t heard back from you, we wanted to check in to see if the resolution provided helps?

If you’re still facing any issues or have additional questions, please don’t hesitate to let us know.

We’re here to help and would be happy to assist further if needed. Looking forward to your feedback!

Thanks,

Prashanth Are

MS Fabric community support.

Did we answer your question? Mark post as a solution, this will help others!

If our response(s) assisted you in any way, don't forget to drop me a "Kudos"

[qmestu]

It does not.

[lbendlin]

My data is 3 tables that are merged

Try not to do that. See if you can join them in the data model instead.

[qmestu]

Not possible. I need to merge them as they need to have the same structure as other existing data.

[lbendlin · Accepted solution]

That's not merge, that's append.