I just realised Other User allows you to check against a specific users email. Bugger.
It is interesting that when you click 'View as roles' there is a 'None' and an 'Other user'.
Other user' is defined nowhere and we don't have the ability to set the rules on it... so why have it? Maybe they are preparing for this feature and allow us to set a rule against 'Other User' that is defined to anyone that has accessed but not yet given a role.
I agree with this aswell. It should be something like 'User Level Security' where anyone that has not been assigned a role can have their data scoped down by attributes found on the Username() model.
For example 'email@example.com' accesses the report and has no role assigned. Behind the scenes PowerBI finds my Username().
Option 1. Username() inner joins on my User model by matching Username() -> User.email. All other models are inner joined on User therefore all data is then scoped down by the single entity User that has been matched by Username().
Option 2. Username() itself in AD has fields such as Division, Region or even Role etc and rules can be set (similar to existing RLS Table Filter rules) that utilise the value of these fields.
Under Option 2 you might have a rule on the Region table that sets Region.Code = Username().RegionCode.
This way anyone logging in, that has no role assigned could have filters applied based on the User Level Security filters.
I'd then simply be able to set my rules by user and expect my 1000+ members to be scoped down based on those rules and their attributes can be managed centrally in AD.
This is how it is done in web frameworks such as Ruby on Rails (see the Pundit Gem or CanCan)
This idea may solve this problem where you want to set rules across a range of users based on attributes of that user.
It may circumvent the need to manage the individuals and roles in a CSV for upload.
This may be similar to this request where we are trying to get User specific filters for RLS https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/15684009-add-a-default-role-for-row-level-security
You may need to raise a feedback request rather than feature request for this. Maybe try StackOverflow or the PowerBI Community Forums.
Hey everyone – just wanted to post an update and say that this work item is still in our roadmap. We are focusing our efforts in enabling other critical features related to filtering such as personal bookmarks in the Power BI service. Thanks again for patience and feedback!
This would be very valuable for models that have foreign keys for example:
Tickets that have many users using CreatedById -> UserId. As alias 'Creator' That is the default association.
Tickets that have many users using AssignedToId -> UserId. As alias 'Worker'.
Tickets that have many users using UpdatedById -> UserId as alias 'Editor'.
Is version control important? You don't see it in VBA, you don't see it in Power Query Formula Language. Corrupted workbooks mustn't be an issue for many people.
Thanks for the renewed interest, everyone! This is certainly something we would like to get to in the future, it’s down to a case of prioritization and working through some implementation details. Keep voting to help move it up our list!
Ah I was wondering why this functionality was gone. It was a good hack :)
Is this in? Pretty sure it is in.
Yeah this seems like such intuitive nature of the user. If I see a pinned tile that says "Users managed by XYZ" and a big count of 10. I want a way to drill down to the filtered table that underlies that tile.
Checking w/ the team where this is at.
So odd that this is in Power Query but not Power BI Desktop. Doesn't matter. I can't login to the Power Query one anyway :(
It has my vote. The current text box takes up room and you also can't adjust the line height which means two lines of 8 font text still takes up a lot of room. I'd love to be able to just add an icon of an 'i' so that when they hover over it some text pops up that adds extra details. The current size of the canvas is so small to begin with to space is precious.
Hey all – we’re looking into how best to tackle this and other filter-related functionality.
If you have a few moments, please take the following survey to share your thoughts. The survey takes ~10 minutes to complete, and will help ensure that what we’re building meets your needs. We appreciate your feedback!
- PQL (PQL or Peequel - )
- MQL (MQL - M Query Language)
- M MQL (M Mashup Query Language )
- M^ (MPower)
- M# (M Sharp)
- #M (But that would break in Twitter :))
- MIQ (M IQ)
- MSM (Microsoft M)
naming things is hard :)