I'm working with a client to try and add Field Level Security to the Vendor EFT Bank Maintenance window. The client would like to set the Bank Name, Transit Routing Number and Bank Account Number as 'read only' or 'view / cannot edit" for some GP users.
I created a separate field level security ID for each field and selected the Vendor EFT Bank Maintenance option under Dynamics GP > Purchasing in the Security Maintenance window. I tried the "Lock Field" and "Disable Field" options for Security Mode, however when we applied this rule to a user, we could still edit the field.
To make sure I selected the right Form and Field name, I changed the Security Mode to "Hide Field" and applied it. The field disappeared from the EFT window.
I feel like I've selected the right form and field but I don't understand why the other security modes are not working. Does anyone have a thought on what might be causing this issue?
Thanks - Ron
*This post is locked for comments
Hi Ron,
Unfortunately the lock or disable options will not work for all fields in Field Level Security. If a field has Dexterity code that changes the state of of the field, the dexterity code bypasses/overrides the security mode specified by field level security. This code normally runs after the window is opened. In my own testing I was able to use the Password before option, which did work for me. You can give that a try in your system.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,902 Super User 2024 Season 2
Martin Dráb 229,316 Most Valuable Professional
nmaenpaa 101,156