Tony Valentine on 05 Aug 2016 23:32:21
When clicking "Analyze in Excel" on a dataset connected to an on-premise data source with the gateway, the ODC file generated points directly to the datasource rather than routing through the Power BI API like the in-model dataset does. This is generally a local connection string that would not work for external users. Also, it effectively circumvents the user name mappings we have created on the gateway data source. Ideally there would be an option on the dataset to have the ODC file either point directly to the datasource or route through the Power BI API & Gateway.
- Comments (5)
RE: Route "Analyze in Excel" ODC through Power BI API & on-premises Gateway
Really a pain this one, we have had some reports developed by Microsoft but we are unable to use them due to this issue
RE: Route "Analyze in Excel" ODC through Power BI API & on-premises Gateway
2018..
RE: Route "Analyze in Excel" ODC through Power BI API & on-premises Gateway
This is an important feature.
RE: Route "Analyze in Excel" ODC through Power BI API & on-premises Gateway
In addition to my original request, I'd like to request a related feature. Why not also allow a PBIX file to be sourced from a gateway the same way Power BI for the web does? This would make it easier for users to find data sources and avoid issues with connection string sprawl and FQDN/non-FQDN name mismatches. You could then say that if the PBIX file is sourced from the gateway, that then when the user uses "Analyze in Excel", that it also routes through the gateway as is desired in my original request.
RE: Route "Analyze in Excel" ODC through Power BI API & on-premises Gateway
This feature is a must for true mobility of enterprise users, whereas Excel serves as primary UI for accessing the data in Analysis Services, and there are no client-server VPN connections used to access internal networks.