Data source error: Information is needed in order to combine data;Information about a data source is

[Anonymous]

Hi,

I started getting this error on one a couple of my dataset refreshes. It refreshes fine in the desktop. Any ideas on what could be causing this?

Data source error: Information is needed in order to combine data;Information about a data source is required.. The exception was raised by the IDbCommand interface.

[enakaleah]

I'm getting this all of a sudden. Files, during desktop design, are set to ignore privacy levels. then publish to online service. check connections again to make them all "none" privacy levels. PowerBi report uses an odata connection to a sales pos and web url to excel files stored in one drive, using oauth login. and all connection privacy levels are set to none, both the odata and oauth. This setup worked for 2+ years, files refreshed daily, and sent report to multple departments. Today it has broken and I dont know why I keep getting this refresh error: 
Data source error: 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. Table: Sales.
Cluster URI: WABI-US-CENTRAL-A-PRIMARY-redirect.analysis.windows.net
Activity ID: 673bf96a-3004-4013-a369-57d7e584c75f
Request ID: 512c520e-1f12-565e-f81e-1732faf3e234
Time: 2023-11-03 21:35:23Z

[v-yueyunzh-msft · Accepted solution]

Hi, @Anonymous 

According to your error message, I checked the relevant problem documents, and the reason is due to the privacy level of the data source configuration.

You can follow my steps below to troubleshoot if the issue is caused by inconsistent "Privacy setting" settings:

(1) You can open the corresponding PBI desktop local file first, and go to the option "Option and Settings-Options" to open this option:

(2) Then you go to "Data Source Settings" and make sure that the "Privacy setting" settings of all data sources connected to your dataset are consistent:

(3) After confirming the consistency, you can perform a desktop data refresh to ensure success.

(4) After the refresh is successful, you can republish to and try to reconfigure the data source definition for the data source of the related dataset to ensure that the "Privacy level" configured on the Serive is consistent with that of the Desktop:

If the above methods cannot help you troubleshoot the problem, you can provide your detailed error information so that we can better help you solve the problem.

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[Kamalesh_K]

Thank you so so much for the detailed explanation and solution. I have been struggling for a couple of days trying different privacy settings, resetting credentials & privacy options on Desktop and Service. Finally with your post, figured it out that we need to update on the Connections also under "Manage Connections and gateways".

[olimilo]

This actually doesn't make sense. In your solution, you mentioned to keep the Privacy Levels consistent between the desktop and service, but it's showing the Desktop Privacy Level set to "None" and the Service Privacy Level set to "Organizational".

Can you explain how this is supposed to be consistent?

[michaelalfred]

Thank you. This was so helpful in solving my problem

[Lawrenceiow]

Thank you, this worked for me. Although, I had to upgrade the gateway (a new version was available) before I was able to save changes at step 4 

[Anonymous]

Thank you!