Forum Discussion
No visuals show in Power BI Service
Hi Anonymous ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you Poojara_D12 BhavinVyas3003 for the prompt response.
You are absolutely right, since you're using OneLake (Fabric) as your DirectQuery source, you don’t need a gateway. But there are still a few key steps to make your report work properly in the Power BI Service:
Here's what you need to do:
1.Fix the OneLake connection error
Go to your workspace > Dataset > Settings.
Under Data source credentials, look for your OneLake connection. Click Edit credentials, select OAuth2, set the privacy level (e.g., Organizational), and sign in. This will bind the connection in the service.2.Web source also needs credentials set
Even if it works in Desktop, the Service requires you to manually set it.
Under the same settings, find your Web connection. Click Edit, choose Anonymous, and set the privacy level (usually Organizational). Confirm it.3.Fix missing parameters
You’re getting that yellow warning because the parameters you used in Power Query don’t have default values, so the service doesn’t know what to do with them.
Open the report in Power BI Desktop, go to Power Query → Manage Parameters, and make sure each one has a default value.
Save and re-publish the report. Then go back to Service > Dataset Settings, and you should see the parameter section appear with editable values.Once you complete these three steps, the report should start showing visuals properly in the Power BI Service just like it does in Desktop.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thank you.
Super UserHi Anonymous
The error you're encountering in Power BI Service—"We are unable to access some data sources because the artifact is missing connection details"—occurs when Power BI cannot access the underlying data sources after the report is published, even though it works fine in Power BI Desktop. This typically happens when the report uses DirectQuery and Web data sources, which require specific configurations in the Power BI Service. For DirectQuery connections to on-premises sources like SQL Server, a properly configured on-premises data gateway is essential. You must ensure that the gateway is installed, online, and that the data source (with exactly matching server and database names) is registered in the gateway cluster via the Power BI admin portal. Then, in the dataset settings in the Service, you need to map the report's dataset to that gateway connection. For Web sources, you may need to manually edit the credentials in the Power BI Service and specify the correct authentication method (e.g., OAuth2, Anonymous, or Basic). If you're using parameters in your Power Query for dynamic URLs or database names, ensure that those parameters are correctly defined and have default values that the Service can use. These steps help Power BI Service "bind" the dataset to the actual data connections required for scheduled refreshes and live queries. Once everything is configured correctly, your report should start working seamlessly in the Service just like it does in Desktop.
Hi Poojara,
Thanks so much for the solution. I sitll have question: my direct query is from oneLake not on-premise, so I don't think I need to configure the gateway,right? Like you said I have edit the Web authentication method as Anonymous in the service. And I do use parameters in the Power query, and I set credential in the destop, but I have no idea on how to define in the service.
Nefertari