Power BI Embedded - Connection to Analysis Services Tabular
Please provide the ability to connect to Analysis Services (Tabular) from Power BI Embedded
As of June 2017,
The Power BI service and Power BI Embedded came together to offer a single API for embedding your dashboards and reports.
This means you now have one API surface, a consistent set of capabilities and access to the latest Power BI features – such as dashboards, gateways and app workspaces – when embedding your content.
You can read more about it here- https://powerbi.microsoft.com/en-us/documentation/powerbi-developer-embedding/
For those who work with the Power BI Embedded Workspace Collection solution, we built a migration tool for easier data transition.
See more info here- https://powerbi.microsoft.com/en-us/documentation/powerbi-developer-migrate-tool/
PBIE won't have this now with PowerBI premium. THat's why they went dark on you a few months back.
Ana Martinez Cabrera commented
Queremos trabajar con Power Bi, para nuestros clientes, necesitamos asesoria y orientacion para saber que productos podemos necesitar para las ideas de desarrollo que tenemos.
Ana Martinez C - Colombia - 310 700 59 57 - email@example.com
Andy Wilbourn commented
We took would like the feature, but proposed a design to the team to allow the gateway to be configured so we can pass along a DAX filter in order to apply an appropriate filter for the data as our users are authenticated via CA Siteminder for our site. We do not want to have to build AD accounts for thousands of users to be able to take advantage of row level filtering in the cube itself.
We want to use Power BI Embedded but cannot until it supports live connections to SSAS. Can we please get a timeline on when when this feature will become available?
Until the feature above becomes available, we would use a different approach which is also problematic. We have many users that want to connect to our SSAS but we do not want to put them on our local domain controller. We only want them to have Azure AD. In order to give them access to the cubes and apply permissions properly, we need to use CUSTOMDATA(). The "Map User Names" feature seems to do what we need but we have a few issues with it. (A) It requires all the usernames to be entered manually into each gateway connection. This is a lot of manual work. Being able to do this from the REST API would really help us streamline this process. (B) The mapping seems to take only the first rule that applies. I'm not sure if this is by design. The documentation doesn't explain it. We would like to be able to apply multiple rules to the same username so that we can map it to multiple permissions (e.g. location, department etc.)