Forum Discussion

BrianDunk's avatar
BrianDunk
Qrew Cadet
6 months ago
Solved

Custom Rule to Prevent a Role Access to Specific Records

I am trying to create a custom rule for a specific Role that prevents this role the ability to view specific records using the Record ID field.  For some reason I can get this to work for one record, but when I add an additional record ID it seems to break.  Can anyone tell me why and what I am doing wrong?

In the screengrab below, If I only have one Record ID look up (1643) line it works fine.  When I add the second Record ID for 1881 this seems to break the rule.

 

Thanks,

Brian

other
  • hueyal's avatar
    hueyal
    6 months ago

    Try changing the condition from 'any' to 'all'.  If you have both with any, it would always be true.

4 Replies

  • Jeff_Richey's avatar
    Jeff_Richey
    Qrew Cadet
    6 months ago

    Brian,

    In addition to the change suggested by hueyal, you might also consider changing your condition to use "is not equal to" rather than "does not contain" because once your database grows large enough your rule will exclude unintended records such as 11643.

  • hueyal's avatar
    hueyal
    Qrew Cadet
    6 months ago

    Try changing the condition from 'any' to 'all'.  If you have both with any, it would always be true.