I have read many, many posts and none seem quite to fit my particular scenario - hoping somebody can assist with a simple straight forward, scalable, maintenance free option …
I have a dataset with many fields, one of which is a comma delimited list of user ID values (built in SQL as a View) (usersList).
I have no restrictions of any user seeing any of the 10’s of Million records being visualized. I do not want to deal with RLS.
I have no concerns of “restricting access”, merely trying to find a default “Filter” that gives any user their 10 or 50 records out of the 10’s of million, but they can still get to the others if they really want to see more … without them needing to set filters from the Controls each and every time they come into it.
We use embedded dashboards in our own front end application.
Users are too dynamic to be forced into a dynamic dataset as I have read in most responses to try and match up users.
I’d like to set a parameter (or whatever component is needed) to be the logged in user; assign that value to a filter (“usersList contains”) and have the visuals show that user the filtered down, limited list of data records that apply to them to go off and work on ….
Isn’t there an easy setting here to be able to recognize the user and filter the dataset without a ton of extraneous effort to create unmanageable other datasets and controls?
Thanks in advance if anybody can simplify this down to allow me to get on with it.
If you don’t want to use RLS, the other way to do this is by using dynamic parameter defaults but that would still involve creating a dataset that contains a mapping of users with their default values.
Can this be converted to a feature request then? There is a function to get the logged in user, there is a single value default capability, how about allowing that function to be used to get the user into the parameter? This seems like it should be MUCH easier to allow filtering based on the user without making that user put his/her ID to start it out each time … without all the management of keeping a list of users that relate the user to the user id.
There’s no function to get the logged in user. If there was such a function, how would you use it to set the default value? Wouldn’t you then need to create a calculated field to do that for every user?
If logged in user is A, set default value of parameter to 1.
If logged in user is B, set default value of parameter to 2, etc.
Thanks @David_Wong - I guess all the many posts I have read were grossly misinterpreted on my part. If there had been a function, the thought would be that the function be callable within the parameter to set the value of param to the user name - no calculated field needed. No unmanageable datasets of keeping a list of users current - just “who is logged in”. Then I can filter my visual in the “usersList contains” style against the field in my dataset.
Guess I will have to approach this as an empty default parameter, and since I come into the dashboard from our own web page, preprocess who is logged on in our web page and pass the parameter in the URL to then filter the dashboard tab visuals I send them to with that link ….