Field Security

Hi All,

E9.05.702A

We are trying to lock down the Group field in Job Entry (JobHead.ProdCode) to only allow certain people to make changes to what defaults in from the part.
I assumed that field security would be the way to go but regardless of how I set it up the field remains updatable for all users.

I set the default option to Read, ensured that the test user account is not a security manager (not sure if that matters), and I made sure to log out and then back in…just in case.

Am I looking at field security the wrong way? Is this a known issue?

JOE ROJAS
Epicor Applications Manager
VENTION MEDICAL + DESIGN & DEVELOPMENT
Advancing Your Innovations For Health

261 Cedar Hill Street | Marlborough, MA 01752
DIRECT: 508.597.1392 x1625 | MOBILE: 774.826.9245
EMAIL: JoRojas@ventionmedical.commailto:JoRojas@ventionmedical.com | WEB: ventionmedical.com http://www.ventionmedical.com/

THINK QUALITY. BE QUALITY. GO BEYOND.

This communication may contain information that is confidential, proprietary or exempt from disclosure, and is intended only for the use of the individual and/or entity it is addressed to. If you are not the intended recipient, please note that any other dissemination, distribution, use or copying of this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately by telephone or by return e-mail, and delete this information from your computer.

I initially missed the part where you stated your test user wasn’t a security manager so I withdrew that point.