133 votes16 comments · Power BI Ideas » Gateways (Enterprise and Personal) · Flag idea as inappropriate… · Admin →
Please, please, please do this. We are racking lots of VM costs just to run the gateway! Although I suppose it's good for the Azure business :P
53 votes5 comments · Power BI Ideas » Gateways (Enterprise and Personal) · Flag idea as inappropriate… · Admin →
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.
56 votes8 comments · Power BI Ideas » Gateways (Enterprise and Personal) · Flag idea as inappropriate… · Admin →
I would love to see it at both the gateway and data source level, with the data source level overriding anything at the gateway level. This way if for some reason you did need different mappings per data source, then you could still do it.
Well msmdpump.dll is not supported but it appears Power BI has added the capability to map usernames. If you go to the Data Source Settings and toggle to the Users tab, there is a button called Map User Names which lets you alter the EffectiveUsername string via custom mappings. Thank you MSFT for adding this feature!!
This still does not work with the release version of Power BI Analysis Services Connector. It fails with the same 404 error. Any update on where this feature is on the priority list?
Thanks for the response. I would think it is minimal work to make msmdpump.dll work, but I can't say since it's not my code. As far as I know, all other Microsoft products that work with SSAS connections support msmdpump.dll, so for consistency alone I think it would good.
Translating identities would be nice because it provides any provider who is hosting an SSAS based solution for a client to provide data via Power BI without having a robust and expensive web API that the big guys have (SendGrid, Zendesk, etc).
Yes, I can access the AS server using the HTTP pump in Excel and SSMS. It's bit complicated, but the reason I want the pump is I want to allow users on external domains to access our data warehouse. We provide our clients a hosted BI solution. I can easily write a proxy web application for the pump that will take the EffectiveUsername from their domain (client\username) and convert it to our domain via a lookup in LDAP (we can store their local AD name in a AD field in our domain). I have done a similar proxy in the past to add certificate based authentication for the pump. However, if the Power BI will not allow me to use the pump, then I have no way hijack via a proxy to convert the EffectiveUsername to our domain. Here is a link to someone who did something similar to my proxy... https://code.msdn.microsoft.com/SSASProxy-Custom-HTTP-7db6d016#content