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)
RE: Allow default filtering based on current user
Desperately need!!! We don't want to use security because we want to allow users to see all reports. But instead default to their view to avoid having to drilldown into the reports every time.
RE: Allow default filtering based on current user
Really need this feature!
RE: Allow default filtering based on current user
Mandatory feature !!!
RE: Allow default filtering based on current user
yes we need this!
RE: Allow default filtering based on current user
Mandatory feature
RE: Allow default filtering based on current user
Yes I would like to see this feature available in the mobile app as well. A sort of "default state" or "favorite" view specific to the current user, that they can configure and save. Then open back up later in as few screen clicks as possible.
RE: Allow default filtering based on current user
Very much needed!
One example of what we need is to look up the current user's office and set the office slicer to default to that office. We do not want to restrict the user from selecting other offices. Just save them the clicks of having to select their own office every time they go into the report.
Add a section under formatting for a slicer and allow an measure or DAX code to be entered.
RE: Allow default filtering based on current user
Ditto, very needed feature, similar to default member / username function in MDX.
RE: Allow default filtering based on current user
Really need this feature for personalized Reports and Dashboards!
RE: Allow default filtering based on current user
(This would be entirely distinct from security, since it wouldn't *hide* non-matching rows, but just slice to the matching ones for tables on which it's enabled.)