Outside of Approval Maps, is there a way to restrict Users to post their own Transactions (without Review from others)?
I think Approval Maps is probably the best way to go, but wondering if anybody encountered this before and solved it?
Thanks!
Solved
Restricting Users from posting their own Transactions
Best answer by krausef77
Chris Hackett wrote:
Hi
We created a simple Customization to add an Owner Field to Journal Transactions and utilizing the Reports To Field on the Employee Record to avoid writing Approval Map Rules for each Employee or Department.
So a combination of Customization and Approval Map on Journal Transactions.
Not ideal but it is what it is.
+8Iqra ~ If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*. Proud Acumatica MVP (2024, 2025) - See my journey here: https://community.acumatica.com/community-site-discussions-150/iqra-harrison-acumatica-mvp-2025-28977
1 person likes this
Chris Hackett wrote:
Hi
We created a simple Customization to add an Owner Field to Journal Transactions and utilizing the Reports To Field on the Employee Record to avoid writing Approval Map Rules for each Employee or Department.
So a combination of Customization and Approval Map on Journal Transactions.
Not ideal but it is what it is.
+10I am guessing you are referring to Journal Transactions. You gave two options: 1) using Approval Workflow 2) implementing a small business logic so the release button is disabled or hidden if the creator of the document is the current user. This can apply to documents other than JE too.
Reza Aghaei CPA, M. Acc. & Acumatica Customization - If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
1 person likes this
Hi
Thank you.
+10If you have a local instance of Acumatica run a select statement on Batch table to see if OwnerID is among the field. If you don’t have a local instance, then create a simple GI on Batch DAC and in the fields check if OwnerID exists.
Regardless, OwnerID is nothing but the ContactID of the user. You have CreatedByID field in the Batch DAC which is the user who created the record and from this you can get the ContactID
Reza Aghaei CPA, M. Acc. & Acumatica Customization - If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
1 person likes this
Reply
Most helpful members this week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.