Forum Discussion
Semantic model uses default data connection - semantic model connecting to data warehouse
torishriver To fix this error just follow the below steps
1. Go to Dataset -> Settings
2. Under the Settings you can find Gateway and Cloud Connections
3. Click Create Connection
4. Under here you have to create a new connection and provide your SQL Server string and your credentials, authenticate it and click Create (located at the bottom)
5. Once created go back to your dataset settings and under Gateway and Cloud Connections choose"New_Connect" (in my case)
6. Now you should be able to refresh the model
Thanks,
Jai
torishriver To fix this error just follow the below steps
1. Go to Dataset -> Settings
2. Under the Settings you can find Gateway and Cloud Connections
3. Click Create Connection
4. Under here you have to create a new connection and provide your SQL Server string and your credentials, authenticate it and click Create (located at the bottom)
5. Once created go back to your dataset settings and under Gateway and Cloud Connections choose"New_Connect" (in my case)
6. Now you should be able to refresh the model
Thanks,
Jai
That seems to have worked but I'm now receiving this error-- do you have any idea what to do to fix this? I can't tell if it's having a problem with none vs organizational privacy levels but it's failing to refresh regardless of which privacy level I set the gateway to:
Information is needed in order to combine data. Please specify a privacy level for each data source.;Information about a data source is required.. The exception was raised by the IDbCommand interface.
Hi torishriver , Thank you for reaching out to the Microsoft Fabric Community Forum.
When you publish a Power BI semantic model that combines data from more than one source, the Power BI Service enforces stricter rules than Desktop. Desktop lets you bypass privacy settings with Ignore privacy levels, but the Service does not. That’s why you’re now seeing the error asking for privacy levels and credentials.
The first step is to make sure that every data source in your model is properly mapped in the Service. Go to your workspace, open Dataset Settings -> Gateway and cloud connections and confirm that each source is linked to the correct gateway or cloud connection. The connection details, especially server and database names, must match exactly with what you used in Desktop, even small differences like using an IP address versus a server name can break the mapping.
Next, set explicit credentials and privacy levels in the Service. Under Dataset Settings -> Data source credentials, edit each data source, re-enter the authentication method (Windows, Microsoft or SQL login) and assign a privacy level. In most organizational setups, Organizational is the right choice, but you can use Private or Public if appropriate. You’ll also want to edit each data source inside Manage gateways and assign the same privacy level there. Power BI requires that every source has a defined privacy level before it can combine them.
If your model merges or appends tables across different systems, you may still encounter issues. Push those joins into the database itself, for example, create a SQL view in your warehouse that combines the tables and then connect Power BI to that single view. This reduces cross-source privacy checks and usually makes refreshes more reliable.
Finally, if the refresh still fails, check the Refresh history in the Service. The detailed error log will usually point to the specific query or source that’s missing a privacy level or credential. That way you don’t have to guess which one is causing the issue.
Data refresh in Power BI - Power BI | Microsoft Learn
Privacy levels in Power Query - Power Query | Microsoft Learn
Set privacy levels (Power Query) - Microsoft Support
Add or remove a gateway data source - Power BI | Microsoft Learn
View and manage on-premises data gateways - Power Platform | Microsoft Learn
