Forum Discussion
We don't support settings for this dataset
All,
I'm hoping to get some help with the issue "We don't support settings for this dataset." Here is a brief background of our configuration:
1) We have MS SQL Server that hosts a number of databases.
2) We created a separate data warehouse database.
3) In the data warehouse db, we created views that rely on other databases.
4) We installed PowerBI Enterprise Gateway and configured it to connect to the data warehouse db. (Connection is successful and online).
Everything seems like it’s configured correctly. I created my PowerBI dataset and Reports and tried to publish the results, however, I get the error: "Publish succeeded, built the published report cannot connect to the data source because we were unable to find a gateway. Please install and configure an enterprise gateway." After doing some more digging, I checked the settings in the "Manage Gateway" section on app.powerbi.com and everything looks good. All connections are successful after I clicked "Test All Connections." I then checked the DATASET SETTINGS for the data set I uploaded and found the following error: "We don't support settings for this dataset." This is where I get stuck.
To give you even more background on our setup, I initially wanted to use the tables in the respective databases to create my reports. However, when I tried to create a report in PowerBI that required the tables cross filter direction to use Bi-Directional cross filter ("Both" instead of "Single). The problem with this is that DirectQuerry does not support "Both" cross filter feature. To get around this, I decided to create a view in MS SQL data warehouse db and that helped me successfully publish to PowerBI. My next step was to install the PowerBI Enterprise Gateway and that is where I ran into this issue. I am afraid that the Enterprise Gateway does not support connection to data sources that are views.
Any help will be appreciated!
Cheers,
-Horia
16 Replies
- walid
Advocate I
I don't have the answer, but wanted to add to this topic my experience so far.
1- Installed Power BI Enterprise Gateway.
2- from Power BI desktop chose DirectQuery.
3- selected one table from Ms SQL server, that is connected using IP address.
4- published to apps.powerbi.com
5- I can see the data in a very simple report that counts number of records.
6- number doesn't refresh by itself while display the dashboard on apps.powerbi.com
7- number doesn't refresh in Power BI desktop.
8- in the corner of power BI desktop shows DirectQuery: enabled.
9- when i open the dataset it says: {
Power BI
We don't support settings for this dataset. Learn moreabout data sources that currently support refresh.The enterprise gateway SD Warehouse is online.}
10- Refresh history shows it is successfull on demand
11- Power BI
This dataset connects to a source with DirectQuery, which is always up-to-date. You don't have to schedule a refresh on this dataset12- Have to click on " ... Refresh Dashboard Tiles" to get the new data.Is there a way make it work?Regards,- jessewysong
Helper III
That is my experience exactly, thank you for tghe detailed breakout.
- horiagrosuRegular Visitor
All,
My colleague and I solved this issue. When you configure the Power BI Enterprise Gateway it will ask you to type in the datesource server. Make sure you use the IP and not the Host Name!
Cheers,
-H
- jessewysong
Helper III
Hello,
I am getting the same error on reports and data I published to a particular office 365 group workspace, but not to others. we are running an Enterprise Gateway to an on premises SQL2014 database. Since both are from the same data I think I must have setup some of the reports wrong. When I mouse over the data set in the sidebar, where I would normally see things like "Schedule Refresh" I see the following text:
"This dataset connects to a source with DirectQuery, which is always up-to-date. You don't have to schedule a refresh on this dataset"
Since the data set hasnt refreshed in over a week, and manually refreshing the report does nothing in the browser, I feel I must have missed smoehting. Any suggestions appreciated. Should I start over and supply an IP instead of the path for the on prem gateway? Im confused why its only an issue within this group.
Best,
- horiagrosuRegular Visitor
Jesse,
I do recommend to reconnect using the IP address instead of the host name. Let me know if this solves your issue if not we can try to troubleshoot further.
-Horia