* For example, a visualization of sales data needs to reflect the policy that account managers can only read sales data for their region.
* For performance reasons, this is enforced at the source by injecting predicates into the query based on the end users identity. If identities for end users are not passed down the process chain into the data layer, it leaves us little option but to publish individual reports for every region, which results in an explosion of complexity and numbers of reports, or move the whole model to BISM and manage the policy in yet another place (namely the BISM model).
blocking migration to SPO/BI Sites. At least 412 Site Collections with more than 600 Power Views. Impacting Adoption or migration for majority of BPUs - e.g. Finance, LCA, HR, etc
Reoccurring problem every time I look at any of the prebuilt PowerView, PowerBI, etc. frontends for SSAS. If you were doing front end application development yourself, then you can weave the user context into the query.
Thanks for setting this to "Started"
Thank you !!!
Can anybody advise me how control the default filter according to the logged-in user
100 votes if it was possible..really really need an option to pass the current user as a parameter to the query or a hidden filter to the reports.
I have the same problem...how to filter data according to the logged-in user
I tried DAX USERNAME () now, but in Power BI Service it returns "guid" which is the same for all users i our tenant. So this does not work !!!
This is a NEED.
For us that works with all the company data at the BI. We need to do a big work around Data and Power BI to create a specific dashboard for each login. While we could only limit acess to one Big Data BI...
Waiting on this feature before implementing Power BI as part of our company information system.
In my opinion. PowerBi should not be considered an enterprise application without the ability to filter data based on the logged in user.
Administrator on 8/16/2020 2:15:30 AM
Hey all! We've continued to make progress here, so I wanted to update this thread with our current capabilities for maintaining security on dashboards/reports. As always, all of this information can be found in our Row-Level Security (RLS)documentation: https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-rls/ > If you have set up RLS in Analysis Services, Power BI will send the signed-in user's credentials to Analysis Services, and respect the RLS rules set up on the on-premises model. > Separately, you can set up RLS in Power BI for data sources that you import or connect to via DirectQuery. This process starts in PBI Desktop, where you define roles, and write DAX to constrain what data these roles can see. As part of this process, can you use the UserPrincipalName () DAX function to get the current signed in user's UPN (e.g. email@example.com). Then, once you publish to service, you can assign users to these roles. Does the above meet your requirements? Please let us know via comments or e-mail. Those of you who requested that the identity of the signed in Power BI user be pass through to Azure SQL, SQL DB, DWH, etc.: we hear you - that is under consideration. Thanks, -Sirui