Skip to main content
Solved

Cannot open this record for editing. The form PR20300 does not contain it.


Acumatica 2021R2 - the Admin user can open the Employee Payroll Settings form w/o and issue.  We’ve added two users with the Administrator role and both are experiencing the error:

Cannot open this record for editing.  The form PR20300 does not contain it.

What can cause this error?  I’ve tried adding all the PR Roles to my own User ID but still experience the same issue.

Hoping the community can point me in the right direction.

Thank you,

MIke Lupro

Best answer by vkumar

Hi @mlupro87 

Error is coming up due to Company/Branch access role not assigned to the user. 

I could replicate the issue on my demo instance. Assigning Company/Branch access role resolves the issue.

  • Check the Company/ Branch profile and identify the ‘Access role’
  • Assign those roles to the user 

 

Hope this helps,

Regards,

View original
Did this topic help you find an answer to your question?

10 replies

Forum|alt.badge.img+8
  • Semi-Pro I
  • 715 replies
  • December 17, 2021

Hi @mlupro87 I created a “test” account and was able to replicate the issue. Are you getting the same when trying to click on an Employee ID? Please confirm.

 


  • Author
  • Jr Varsity III
  • 21 replies
  • December 17, 2021

Yes, it happens when I click on an employee ID.


  • Author
  • Jr Varsity III
  • 21 replies
  • December 17, 2021

I filed a case with Acumatica #219889 so we may get an answer in a couple of days.


Forum|alt.badge.img+12
  • Acumatica Support Team
  • 866 replies
  • Answer
  • December 18, 2021

Hi @mlupro87 

Error is coming up due to Company/Branch access role not assigned to the user. 

I could replicate the issue on my demo instance. Assigning Company/Branch access role resolves the issue.

  • Check the Company/ Branch profile and identify the ‘Access role’
  • Assign those roles to the user 

 

Hope this helps,

Regards,


  • Author
  • Jr Varsity III
  • 21 replies
  • December 18, 2021

Assigned myself and my associate to the Branch Access role and issue is resolved.  THANK YOU.

Mike Lupro

 


Forum|alt.badge.img+12
  • Acumatica Support Team
  • 866 replies
  • December 18, 2021

@mlupro87 you are most welcome!

 

 


  • Freshman I
  • 11 replies
  • December 22, 2021

I am seeing this issue as well - but in the bank reconciliation screen.  The error is thrown when trying to open a closed rec.  I confirmed the users have access to all the roles for company access and the error still occurred. I then turned off the “restrict visibility by branch” feature and now we can open those closed recs. It is inconsistent behavior however as a number of their other bank accounts have this feature turned ON and we have no problem getting into closed recs.  Any ideas?


Forum|alt.badge.img+12
  • Acumatica Support Team
  • 866 replies
  • December 23, 2021

Hi @lbrewster57 

That has got to do with the branch you logon to.

  • If you logon to a branch that is not linked to the Cash account,
  • and Cash account has ‘restrict visibility by branch’ enabled,

it wont allow you open the Bank reconciliation statement for above Cash account. Here are couple of screenshots to explain this : 

In this case, ‘restrict visibility by branch’ is enabled on Cash account 10700 and its linked to Product wholesale branch.

I logged on to another branch and tried to open the reconciliation statement.

Hope this clarifies,

Regards,

 


  • Freshman I
  • 11 replies
  • December 23, 2021

Hello!  Thank you for the reply.  I did figure this out shortly after I wrote that post - but it is certainly helpful to have the screenshots you added for the community to see at large.


Forum|alt.badge.img
  • Freshman I
  • 21 replies
  • September 11, 2023

@vkumar I have the same issue but from the sales order screen SO301000.
 

We have 3 different order types.
2 of them give this error message but one of them does not.

 

Thanks
Sam

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings