I just tried adding some field security to the VendBank table, to set the fields that appear in the “Bank/Remit To” tab of the Vendor Maintenance screen read-only for a particular group.
In classic mode, everything works fine. The fields are read-only, and I cannot create new records (since the required fields are read-only).
In Kinetic mode, it kinda works. The fields do not appear as read-only on screen, but if I try modifying an existing record, nothing is saved. However it also allows me to create new records, and saves without issue on those.
BTW this is in 2023.2.9.
Is this a known issue, or am I missing something? Seems to me like a pretty important feature to be not working properly…
Went to use field security for the first time today. Glad I got to spent 2 hours debugging this wondering what the hell I was doing wrong. Still absolutely mind melting they let bugs like this get by and exist for so long.
Has anybody developed a workaround for this? I asked support for a status on this issue and they actually gave me a different problem number, but looks like the exact same problem (PRB0276842).
I am imagining I could write a function to check the field security against the current user, call it on form load, and return a value that could be stored in transview and then write a data rule to disable the field based on that value. I just feel like its a lot of work and wondering if somebody came up with a better idea.
