Users Receiving Permission Denied Messages for Data That They Should Be Allowed to See

More info - 

In a realationship   Items -> Child Items -> Grandchild Items

A user creates an item, some child items for that item and some grandchild items for the top level item. 

That user is only allowed to see data based on them being the Created By in the top level Items table.

This was limited in the table using Access settings for the Child and Grandchild tables by

when user is  Items - Created by

The error we are seeing is that the user can see data in Child but not in Grandchild, however if I set the access in Grandchild to 

when user is Child - Items - Created by  (a lookup field from the parent Items table)

they can see the data without any problem.

My guess is that you may have made a relationship which skipped a generation from Items to Grandchild, but it is not being populated. 

You can probably delete that relationship and double hop any lookup fields down though the child to the grandchild.

You should make copy of your app first before deleting any relationship if you are not sure if you need it.  ie test before deleting.

Possibly that is the case - but this is a case of the relationship having been working as of Friday and no longer working today (we had a power outage due to weather yesterday).

I doubt a local power failure or the Quick Base data center move is the cause.

It does look like the relationship isn't being populated any more - am currently investigating possible causes.

Once again I would question the purpose of that relationship.  I would just double hop the lookup fields down to the child and from there down to the Grand Child and kill off that relationship which skips a generation.

I'm also seeing an issue in another app - where lookup fields from a relationship appear to have the wrong field names.

Hi Ian,

If you are still having issues finding the reason your records aren't syncing up correctly I would recommend opening a case with our Customer Care Team. This way they can help you isolate the source of the issue. While signed into Quick Base if you click Help > Manage Support Cases > + New Support Case you can create a case with our Customer Care Team and they can help you to find where the disconnect is happening. 

Thanks Evan - will do