This new bug has only been noticed in cases where we’ve leaned heavily on the new Tab Blocks.
This short video example below shows how when we’re customizing a view in a sales pipeline app that uses tab blocks (and nested tabs), clicking “Hide all” does not hide a subset of fields. The issue appears to affect fields created within a tab block, leaving them visible even after the user attempts to turn off all fields, which makes view configuration inconsistent and confusing.
thank you very much for the report! This is indeed quite an interesting issue
Fortunately, it fits very well with something we’re already working on.
The menu you’re seeing here is actually a bit older and was built long before the new record experience and Tab Blocks existed. Because of that, some of the newer functionality doesn’t work perfectly with it.
At the same time, we’re currently extending Field Access beyond the record itself to tables, views, and the other relevant areas. This will make sure that fields are also hidden there when access is restricted and shown again when access is restored.
As part of that work, we’ll most likely rebuild this menu anyway. That should fix this issue directly. It’s often quicker to do that than trying to make all the new features work with the old component. The remaining effort here should only be a few hours.
I’ll keep you posted with an update once this is done.
