Imagine, you have a master screen with a lot of detail tabs and you want to set it to read-only mode, if current user or any state meets some specific condition. You have only one option, how to do it. You have to create row level security rule for every entity in the detail. That’s a lot of work. Yes, there is an option to set the read-only screen to user via application role, but that’s static condition. It would be nice to do it dynamic way and set the screen to read-only mode based on rule condition.
Setting up a row-level-security rule has the advantage that it works then on every screen. So I still consider it beneficial to model it this way even though it is time consuming when there are lots of child entities.
It would be also very hard to invent a place where to put the rule you are suggesting and how exactly it should behave. Should it just turn the whole screen read only based on the master record selection? That would be very limiting in the use cases.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.