We need to be able to control editable of a table field without need to custom code on a page.

This can be solved by a new property on a table field, property that is in line with current property "AccessByPermisson".

The AccessByPermission will control if you can access the field at all.

Another similar property "EditableByPermission" would be solving this for us.

Example:

field(3; "Environment Name"; Text[100])

        {

            Caption = 'Environment Name';

            AccessByPermission = tabledata "G/L Account" = r;

            EditableByPermission = tabledata "G/L Account" = D;

        }

If this is enabled then we can, for example, add a table to our PTE called "Environment Name Editable" and use that table for these properties. That table is a part of a permission set and the permission set a part of Entra Security Group.

This will give us much better control of field level security without code.

And - Both AccessByPermission and EditableByPermission must be available in table extension as "modify" operators.