This solution discussed here, is it possible to create a 3 column mapping instead of 2, meaning each email gets 3 different file attachments, one is filtered to that person, and second simply splits this data further into 3 different categories.
Hi @gmikay ,
do I understand correctly that you want a view with the filtering applied to the person and another view filtered into three categories? Are the categories dependent on the person (requiring RLS), or are they general filters?
Regards,
Nico
Tell me if what I did is correct as I already solved my problem, I created an RLS dataset where UserName I left blank, GroupName, I filled these with the specific groups/groupemails where I tested and saw success, I just had to create 3 different visuals to take care of the second filter. My question is, can you explain to me how UserName and GroupName work together? Are they basically the same field, so if I left the GroupName blank and filled out UserName with the same values would I get the same result? In my case, it’s not necessarily a person, but a group of people per category. Oh and one last thing, could I have used the tag based low restriction instead of user? How do you know which one to use and when?
Hi @gmikay ,
If your RLS rules are based on a group or category (e.g. department) the RLS can work with a group or category as field.
RLS is just a kind of filter. It does not matter which field is used (as long as it is doing the right restrictions).
The tag-based rules are used for embedded dashboards. If you are not handling the users in QuickSight and but you want to restrict the data access depending on the source system where the dashboard is embedded.
You can find more information regarding tag-based RLS here:
Best regard,
Nico
If this helped you, please mark my answer as solution. That helpes the community to find solutions faster.