1 of 1 people found this helpful
Just to let you know, you are looking at the right resource in terms of best-practices for handling row level security in Tableau. Bryant's blog does a fantastic job of collecting proofed solutions, and he keeps them very up-to-date. That said, as the number of IF conditions gets long, it'll become more challenging to maintain and will have an impact in performance (how big depends on many factors, including your the size of your data set, but could as well be unnoticeable). If you don't think the list of IFs will get very long, and you are satisfied on the performance once you've setup the filter and tested it, I'd say you are good to go.
As that blog post ends, there are other solutions worth checking on part 2. The one I've seen most commonly used is CONTAINS, this gives you the flexibility to consolidate several possibilities in a single condition. Worth testing if you are concerned about the number of IFs.
Both blog posts are useful when you are working with extracts. If you are working with live connections, I'd also suggest reading the parent blog post.
Hope this helps!
Thanks Santiago for your assistance! I was about to review the Part 2 but got discouraged when they mentioned the Contains calc would be challenging in the 10.5 version. (We're still in transition to move to 2018.1.1.). I'll take another look.
I know it's very dependent on the type of data set we have, but do you think there is any "rule of thumb" numbers that indicate when the performance gets hit by such calculation? e.g. "starting from 200 IFs conditions & looking through a 10 million rows data set, the performance starts to take a noticeable hit.". It's simplistic I know but I'm trying to get the best opinions before moving ahead.
No worries! I'm not aware of a 'rule of thumb' on this respect. If there are not that many conditions to type, I'd encourage to test it out. Other than that, I'd wait to hear from other members of the community too!