Suggest having the ability for individual companies to be able to control the default gateway behavior for power BI reports both gateway and paginated reports. Currently if the gateway is turned on once for any report, it will be forever defaulted to on for all future reports. Even if the report does not need a gateway. This creates a lot of extra work in having to go back and forth in the setting screen to disable the gateway before a report is usable after publishing to power BI service.
Based on previous conversations with Microsoft support here's a summary of possible solutions:
Based on previous conversations with Microsoft support here's a summary of possible solutions:
- Remember users last choice regarding gateway and default to the choice the user last used.
- This would be the least disruptive to all power bi users globally, as those who always use the gateway would have the gateway defaulting to on, and those who don’t use the gateway it would remain off. For those who play both sides of the gateway, they are used to having to that setting anyways, so it could potentially be a value add for them when they go to set the gateway and see that it’s already set appropriately.
- A global setting in the power bi admin console that allows the power bi admins to set what the default value should be for the organization or perhaps better yet would be an individual setting, since it could be possible one user needs to run through a gateway and another doesn’t.
- Ability to embed a tag or similar attribute that would allow it to be recognized independently from similar datasources that used the gateway.
- Fully qualify the gateway mapping, so that a report can be published and be able to run right away without having to first go and change the gateway setting.
1 Comment
- Status added:New
