Robert Robinson
Reputable Poster
\"Read only\" Row security
This is taking it back a ways...
I am trying to recall how to institute Row Security on company so that a user can view and run reports on a company, but if they try to enter a transaction such as a journal entry, the company field immediately highlights red.
For the companies in question, I set Row security for all tables to View, Yes/Add, Change, Delete No. I then add the new security to a role, and a role to a test user. When i have the test user create a journal entry, the CO field does not light up; however, the security causes a commit failed error (the journal entry never takes). I do not want the transaction to get to the commit stage, though.
Forgive my failing memory, but how is this "read only" security created again? I am doing real well with total lockouts (where view also equals no)...
This is taking it back a ways...
I am trying to recall how to institute Row Security on company so that a user can view and run reports on a company, but if they try to enter a transaction such as a journal entry, the company field immediately highlights red.
For the companies in question, I set Row security for all tables to View, Yes/Add, Change, Delete No. I then add the new security to a role, and a role to a test user. When i have the test user create a journal entry, the CO field does not light up; however, the security causes a commit failed error (the journal entry never takes). I do not want the transaction to get to the commit stage, though.
Forgive my failing memory, but how is this "read only" security created again? I am doing real well with total lockouts (where view also equals no)...