Some native Application field controls (that inherently call specific BO methods) may be thwarting your desired results...
I think you may find you have to apply user role security to BO methods as well to get the desired effect consistently.
...Also remotely possible you have manager enabled BPMs (or native recurring processes enabled) running that do their thing regardless of who the user is (making it SEEM like the db field level security is not working).
Rob
I think you may find you have to apply user role security to BO methods as well to get the desired effect consistently.
...Also remotely possible you have manager enabled BPMs (or native recurring processes enabled) running that do their thing regardless of who the user is (making it SEEM like the db field level security is not working).
Rob
--- On Thu, 4/30/09, craigtcunnington <vantagegroup@...> wrote:
From: craigtcunnington <vantagegroup@...>
Subject: [Vantage] Field Level Security - Hit or miss?
To: vantage@yahoogroups.com
Date: Thursday, April 30, 2009, 8:09 AM
Has anyone had any experience, successful or not, using field level security on specific fields? I am having difficulty with certain fields in the order and quote screen, being configured as read-only. Some work, some don't. Any ideas?