I’m in our Epicor 10.1.400.17 environment attempting to open Financial Management > Accounts Receivable > General Operations > Invoice Entry. The AR Invoice Entry screen opens to the Group > Detail tab. Under Group Information, I click the Group button, search Starting At for all groups. I select the only group available and receive the error message “You are not allowed to open this group.”
I am the user that created those groups.
If I try to open with another user, that specific group I will get the error: “InvcGrp is locked by another user.” which is correct.
My question is why under the user that I’ve created those groups, I am not able to open them?
I cant answer to the why…its an Epicor thing…but what you can do is log off of Epicor correctly…meaning do not hit the red ‘x’ in the upper right corner. Close all screens normally…meaning File --> Exit.
Then when you open it again it usually unlocks it…yes it is bizarre…but this has worked for me in the past…in fact last week it happened.
We also have this problem occasionally in 905702a. I didn’t know that using the red x vs file exit made any difference. Wow! We’ll have to try that next time.
One other thing we have had to do, in case the file exit method doesn’t work, we’ve had Epicor support tell us to run the 10250 AR Invoice conversion to unlock groups.
10250 isn’t in 10.2. Does anyone know if there is an equivalent? Epicor support said to have the user, or log in as them, and File > Exit. Which isn’t that helpful.
We have this occasionally and the file > exit vs Red X makes not difference. This happens even if service connect runs through the invoice group process. What happens is there are methods that run at the moment of dispose of the form. Occasionally there may be an issue running all the methods in a timely manner before windows disposes of the the dll and process. The most reliable way would be use the clear form button. This has yet to leave the group locked. Alternatively what I have done in the past was create an updateable BAQ that we can simple clear the Locked by field. This comes in handy when the locked user is not available.
should you share with us your uBAQ file? I have created one already but I keep receiving the error message saying a different user is locking the Invoice. We are running 10.1.600.33, probably I´m doing something wrong with my uBAQActiveUsr.baq (21.1 KB)
attached you will find my uBAQ approach, obviously it is not working…
I’m attempting to get around this by clearing the form on a FormClosing event. That way, the form is immediately cleared if the user hits “X” or does file > exit.
I believe it is oTrans.Clear() or oTrans.ClearAll() done via a c# application customization. You can use the wizard to create a closing event. I just had this idea today but have not started implementing it yet.
I have always wondered what the use cases of group locking was. Was it some errant dev on their way out putting something in place to just annoy everyone, including the admins, or was it meant to be some form of data entry control.
