At the moment, you can do row filtering in a Data Model, by applying an enforced filter. This works fine in simple scenarios. In my case, I have 150 different users who each need to be able to see only their own data. So I have to add them one-by-one to the data model's "Data Security" area. Not only that, I have to do this to 10 different cubes, so this will be a lot of manual effort to set up and maintain over time as people come and go. What I'd like to be able to do is define a custom attribute on the User record, like "Location ID". I'd fill it in for that user, entering "12345" for a particular user record. That User is also a member of a group called "My Restricted Group". Then, I could go into the Data Security section, add an entry for the Location ID filter, applied to "My Restricted Group", and reference the "Location ID" number. Then the system would enforce it at runtime -- is the logged in user a member of "My Restricted Group"? If so, apply a fiter on the Location ID field, and fill it in with the value in their User profile. Then I only have to maintain the Location ID value in their user profile once, and only need to apply that Location ID filter once per cube, not 150 times per cube.
... View more
