Skip to main content

Power BI

Needs Votes

Allow default filtering based on current user

Vote (173) Share
TL's profile image

TL on 07 Jul 2017 22:48:52

It would be nice, even if not essential, to allow a report to slice by default to the current user's data. For instance, I might envision:

- A dimUser table that can slice by default to the USERNAME () output
- A dimGeo table that can slice by default to the city/state/country of the session's IP address
- ...and so forth

Comments (20)
TL's profile image Profile Picture

4801d900 a568-4f11-8dee-83146553ae9d on 10 Jul 2020 17:20:43

RE: Allow default filtering based on current user

Really badly needed feature.

TL's profile image Profile Picture

e78b0d30 51b5-448a-8470-35b1f15ae6d3 on 06 Jul 2020 00:15:27

RE: Allow default filtering based on current user

I would have used this feature so many times if it had been available!

TL's profile image Profile Picture

0468bac6 a87f-40cf-aee7-cd6794caae68 on 06 Jul 2020 00:12:57

RE: Allow default filtering based on current user

This would be a huge help

TL's profile image Profile Picture

a3309361 99be-ea11-a812-000d3a8ddfb2 on 06 Jul 2020 00:04:15

RE: Allow default filtering based on current user

This is definitely essential. Please add this soon.

TL's profile image Profile Picture

e49e7a14 bfcb-4e92-8a8a-d75e76cd564d on 06 Jul 2020 00:03:19

RE: Allow default filtering based on current user

This feature is very required as the filters don't get updated based on RLS there are lot of bugs raised for the reports which we publish. Kindly consider this on priority.

TL's profile image Profile Picture

a3309361 99be-ea11-a812-000d3a8ddfb2 on 06 Jul 2020 00:01:30

RE: Allow default filtering based on current user

We need a default current user filter. RLS does not meet this requirement as that is a security thing. User can't override RLS, but would be able to override a default current user filter.

TL's profile image Profile Picture

8ec3b571 9b6e-4f77-97cc-06d03c2d1c63 on 05 Jul 2020 23:48:43

RE: Allow default filtering based on current user

We have different pieces of information in a report that are only relavant to certain users. Our booksmarks allow us to use certain visuals . However, we'd like it if we could base this visual view on the username of he individual as opposed to them needing to select it (as many times the viewer does not initially know what to select to see "their" visual.

TL's profile image Profile Picture

fc40176a 5643-4e32-a33b-6958c653fd2a on 05 Jul 2020 23:47:41

RE: Allow default filtering based on current user

Hi,

I created a report were one graph shows information about multiple instructors. I want to show them the result, but don't want anyone see others result. How can I do that

TL's profile image Profile Picture

093c78d9 5d61-45dd-887a-d81397529c5a on 05 Jul 2020 23:46:01

RE: Allow default filtering based on current user

Hi,



I have multiple reports with each reports having two slicers named as the category & Items and all the tables in the data model has the column named as Category. Each report has been bookmarked and linked to a button so that the user can Navigate between the reports.



Currently, I am applying RLS on each report by creating a role for each category. The issue is that I have set up some default value in each slicer in report & created a bookmark for that and linked that to the Buttons.



After applying the RLS to all reports, my both slicers present in each report has the same default value selected as before. My requirement is that Category slicer should have the value selected dependent on the Category Role.



For example, If I have a role Named as category 1, then the Category slicer should have the value selected as Category 1 in all Bookmarked page, If I have a role as category 1, then the category slicer should have the value selected as category 2 in all bookmarked pages.

Please implement this feature ASAP.

TL's profile image Profile Picture

f5505275 c14c-e911-a961-000d3a4f33c1 on 05 Jul 2020 23:36:50

RE: Allow default filtering based on current user

This is essential for any orgs using row-level security and any sort of slicers. Pretty inelegant for users to initially log into a report with blank data, then having to user the slicer to unlock what they have permissions to see.