Help needed to debug an access rule preventing me (owner) from deleting some rows!

This is the table Empresas. It had some 10 records. I was able to delete all the middle ones, but not the first nor the last.

If I try to delete any of these that remained, I get the message
Blocked by Row Update Access Rules

The table Empresa has everything turned on for the owner. And if the email matches they can Update. And even users that don´t match email, I CHANGED to allow reading, updating and creating, and still I am blocked by access rules.

I’m not sure if that’s the cause of your problem, but in your table rules it says user.access in OWNER. As fas as I know, OWNER is a predefined integer, not an iterable, so using the in operator on it directly would probably lead to a TypeError. The rule should probably read user.access in [ OWNER ]. Perhaps that’ll do something?

Changed it to ==

Still can´t delete those rows… blocked by access rules… wtf

What happens if I have a table where for some reason I have no access and it is linked by a reference to this table?

Trying to delete these two rows would try to clean the reference in THAT table, right?

Can you be blocked from deleting a row in a table you have full access because a table you don´t have access refers to the record in the table you have access?

That was it. I had several tables where the rules were, in the order below:

if email matched the user email, then he had access to stuff
if email didn´t match, no access
owner can do anything

Owner rule being third meant the owner couldn´t see the data. Nor update it.

I thought the tables were clean.

But they weren´t. And the records I couldn´t see had references to the table Empresas.

When trying to delete the table empresa, Grist would try to change the other tables (to delete the reference and wasn´t able to.