Field level security

idiot

What would be the best way for the following scenario besides hard coding?

User A is in charge of Purchases & create Purchase Order.
User B is in charge of Inventory finds that the Location, Bin specified by User A for the Purchase Order is full & decides to change Location or Bin.
User B is only allowed to change Location, Bin, but must be able to view most info in the Purchase Order & will post the Purchase Order.
User B is likely to be a non-permanent users, hence prone to mistakes & restrictions must be enforced by the system on accidental changes.

Simply put, all fields other than Location, Bin on the Purchase Order cannot be changed by User B.
The field level security must be enforced thru the Purchase tables?
Although not recommended, any way to control by the form?

Thanks.

diptish.naskar

Two Ways of doing it,

1. Create a seperate form for the USER B and put location code there and remove the same from the form of USER A

2. Customize the same to provide the field level security.

Revolution1210

An article described how to implement field level security, if you decide to go down that route:
How to apply field-level security in Microsoft Dynamics NAV

themave

this is an add-on that provides field level security, we don't use this one, but we use some of there other add-ons, that work well and are reasonably priced

http://www.costcontrolsoftware.com/F_C_Security.htm

idiot

Thanks all.
Looks like there's no getting out of hard coding...