Forum Discussion
Multiple Roles in Row Level Security suddenly starts causing errors for users
We have had our row level security configured like this for a long time. After the December update, suddenly users that are part of two different security roles are getting an error that says "The us...
I had a similar problem that I posted here a few weeks ago, and there are basically 2 solutions we identified.
The first is to create a single security role for each user that explicitly defines which rows of which tables they do and don't have access to (time-consuming but doesn't require changing the data model at all).
The second is to create intermediary tables for any tables in the model that currently have a many-to-many relationship and instead linking those tables to the intermediary table in many-to-one relationships (requires changing the data model a bit, but saves time in the long run and reduces the potential for human error). I described the exact method I used to do that in the update here.