Wild West of Bugs with Table Permissions at the moment...

[scott192]

There seems to be some incredible bugs dropping through the Appsheet system at the moment.

One of the latest to show up is the inability to restructure table schemas if ANY of the tables in your app are set to be READ ONLY.

It may be just me and my apps, but the dreaded error below will show and you will not be able to save your changes.

I don’t know if the error affects different data backends, it is Google Sheets in my case.

I have a work around to set the Tables to READ ONLY without triggering this bug and that is to use the FORMULA setting and provide a text string “READ_ONLY”.

Once you update all your READ ONLY tables to include a formula and save, only then will you be able to make any schema changes to other tables without the bug appearing.

There is a massive caveat if you are previewing the new GMAIL integration as it seems that a brand new INVISIBLE table has been added behind the scenes to deal with GMAIL EVENT ATTACHMENTS.

The above table does not show in my App and I believe it is for the GMAIL EVENT stuff that is broken as well.

So consequently, if you are developing and changing schemas in apps that have this preview enabled then you will NOT be able to make any more schema changes because the above table is set to READ ONLY and is invisible so you cannot do the workaround.

Hope you find this information useful in these current frustrating times.

@Aleksi @nico @lizlynch

[Mathieudkt]

Same issue in Italia

[nico]

Hi Steve, thanks for the report with all the details here. I’ve done a bit of initial investigation based on the details you provided and believe this is a bug related to a rollout of a new caching mechanism that affects some % of users, including you :'(. I’ve routed this to our infrastructure team and they will resolve this shortly.

[James_McFarlane]

My customers app are suffering from this issues also.

[scott192]

Just did a schema refresh in an App with the problem and it has been resolved! Well done guys!

[mateo]

I can confirm that something weird is going on. I got that error many times but it was resolved - now it doesn’t come back but during the development process, I encountered many saving errors. By errors I mean the page is frozen and I cannot do anything but refresh. It is frustrating. Despite refreshing the page or clearing the cache it keeps coming back. It feels like those issues are correlated somehow. I just wanted to let you know @nico and find out if I am correct.