I’m loving the “hide entity view rule” feature! It’s been a great QoL improvement for us. I’m just facing one limitation. I’m trying to hide a couple entity views based off of users’ membership in departments. Users can be in multiple departments (many-to-many relation), so the relation field does not appear as an option for filtering. I have a formula field that lists the departments a user is a part of, but I can only use “is” or “is not” for hiding the entity view based off of this formula field. Having “does not contain” would resolve this.
E.g. Samantha is a part of Recruitment and Onboarding, and Rich is only a part of Onboarding. They have access to the same database, and each department has their own relevant entity view. Samantha should see both views, and Rich should only see the onboarding view. So I want to hide the recruitment view for Rich (hide when User.DepartmentFormula does not contain “”).