Has anyone ever successfully implemented Navision security exclusively through SQL Server roles and permissions rather than Nav / SQL security synchronize process? Problem: client wants a single field in a table to be editable through Navision client without modifying forms etc… based on user role.
This is currently not possible because Navision switches the user’s security context to that of an applicaton role if he is not a db_owner, so it is not relevant what permissions he has been granted in SQL terms, when running Navision.
Thanks for the response…
If you don’t want to change the form, have you thought about code? On the onModify trigger of the field (Table Level if it exsists) filter on the MemberOf table for USERID and Role. If its there then they can edit it, if no throw an exception and tell them they have no permissions to do it. HTH