By using this website, you agree to our Terms of Use (click here)
Hi,
I have had this request a few times so I will ask here and see if anyone has any ideas.
Case: A company want's a user to be able to enter Journal Transactions, but only see their own transactions that they entered when they go to the Journal Transaction screen.
What I have tried:
- I copied the default Journal Transaction screen and created a new GI to view just their own entries. I granted that user access to that GI and blocked all other users. To the user, it looks exactly the same but they only see the transactions they created.
- I blocked that one user from the default Journal Transaction screen.
- I did this as I can create a filtered view of the default screen, but the "ALL" tab is still there and they could click it and see all the transactions
Issues: This user cannot create a transaction, due to the security on the default screen.
Possible options I am considering:
- Hide the "ALL" tab when you have a filtered view. Not sure how to accomplish this though. Via customization I am sure (which is fine)
- Add the user restriction in code for that screen. Again a customization.
Both customization options will be new for me but sure I can figure it out, but open to any pointers on where to start.
Anyways, just wondering if anyone had any other thoughts I may be overlooking?
Appreciate any ideas
One question. Did you set permissions on the Journal Transactions data entry screen to Insert? If not, they would be able to pull up any transaction in that screen using the magnifying glass.
One idea for the Generic Inquiry. Put the filter in the CONDITIONS tab of the Generic Inquiry definition using the @Me filter so the restriction on the user is built into the definition of the Generic Inquiry? This would be instead of using Saved Filters, which, as you discovered, always allows you to access the ALL RECORDS tab.