Bug? Lookup fields cannot be used for custom access rules?

Question

Has anyone else run into this?
I am trying to set a custom rule for viewing records in a table. It is simple: Go to a role, and select custom rule: A record can only be viewed when [Field A]=True.
This works perfect if the field is a scalar field in the record. If it is a lookup field, it works on the very first test, then immediately stops working. If you test it twice, it just never works again. Very strange?? Has anyone else experienced this and have a work around? I have tested with text fields and checkbox fields. Once they are lookup fields, it appears to work on your first test, then stops working immediately.&nbsp;------------------------------Mike Tamoush------------------------------

markshnier__you · Answer

never has that issue ....------------------------------Mark Shnier (Your Quickbase Coach)mark.shnier@gmail.com------------------------------

miketamoush · Answer

After hours of testing....found the user error. It was a field permission set back on a grandparent....sigh.
For other people that may stumble upon this, check to be sure no field used in the custom rule ever points to a field (from a lookup or otherwise) that have restricted field permissions. If that user role can't view the original field way up the parent chain, then of course it wont fire correctly in a future rule...------------------------------Mike Tamoush------------------------------

Forum Discussion

Bug? Lookup fields cannot be used for custom access rules?