Visuals throwing an error and not loading

Q&A
, ,
1

image (9)
image (9)1852×459 14.8 KB

Some users of a dashboard I created have been facing this issue recently, the visuals do not load with the below error. I have been able to resolve it in 2 ways, neither of which are ideal

1/ If I remove the RLS from the underlying datasets, it goes away.

2/ In the RLS dataset, I have a permissions group which is used to give access to all data. If I add the user into that group, they see all data.

It seems like the issue is related to the way the RLS is getting applied but I don’t know how to go about resolving this as the RLS dataset has to have the current rules built in. The dataset has not changed in the last 1.5 years and previously the visuals were loading perfectly fine. The issue has started in the last ~3-4 months and multiple users are impacted.

2

Hi @Pankhuri,
I know this feature update may have happened prior to when you started encountering issues but I wonder if this has something to do with it as this rollout happened earlier this year:

Based on what you mentioned above though, regarding the two ways you’ve been able to resolve; both of those seem to include the removal of RLS rules so the issue must be occurring in how the permissions are being handled.

If nothing has been changed on your dataset or your RLS dataset, then I would suggest creating a support ticket so that you can get more personalized account assistance from the AWS support team.

3

I was able to source some more details on this: The error code is SPICE_IN_LIST_SIZE_LIMIT_EXCEEDED. It indicates that the RLS configuration value for this user is too large, exceeding our current limit.

Any idea how I should approach mitigating this?

4

Hi @Pankhuri,

To my understanding, this error signals that your list of rules has exceeded the size that QuickSight can handle for RLS. This can happen if a list contains too many values that are added to a specific user or group.
Could you explain a bit more in depth of how your RLS dataset is setup. Maybe there’s some way that you can use a grouping field that has less values to handle the restrictions?

5

Hi @Pankhuri

It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.

If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.

Thank you!

6

Hi @Pankhuri

Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.

Thank you!