Skip to main content
Solved

'An entry with the same key already exists' error


Forum|alt.badge.img

Hi, 

I’m new to acumatica. I have customized a form (PI301000) . In this form, there is a grid in the tab like below.

I want to move the ‘Add purchase’ button with the action into the grid toll bar. But when I was trying drag and drop button into the ActionBar - custom items in the project editor, It shows me the below error.

I checked whether there is another action using the same key but this is the only action I have defined except ‘Print report’. can someone help me with this issue please?

Thank you.

 

Best answer by Django

This is the dreaded error when you’re customizing a screen. You might have to add this manually by editing the .aspx.  I’ve had an issue where adding a dialog box would instantly corrupt by screen but I haven’t had a chance to revisit that yet.

I did have this issue the other way re-adding a control to a screen and I found that the screen aspx left behind some XML when I removed the control to re-add it. I edited out the code that was left behind and I was able to add the control without an issue. And from what I could see there were no duplicate IDs but maybe the message was referring to duplicate entity values within the aspx vs a value with ID= that is duplicated.

Have a look at the .aspx before and after you add the control and see if you can identify what the issue might be.

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

3 replies

paulgilfoy13
Freshman I
  • Freshman I
  • 6 replies
  • February 27, 2023

This is a coincidence. I am having the same problem today.
Build 22.208.0012.   
I added a row control onto a Tab. Now, I am getting the same error. 

If I find anything out, I’ll post it here. 


Forum|alt.badge.img+5
  • Captain II
  • 477 replies
  • Answer
  • February 27, 2023

This is the dreaded error when you’re customizing a screen. You might have to add this manually by editing the .aspx.  I’ve had an issue where adding a dialog box would instantly corrupt by screen but I haven’t had a chance to revisit that yet.

I did have this issue the other way re-adding a control to a screen and I found that the screen aspx left behind some XML when I removed the control to re-add it. I edited out the code that was left behind and I was able to add the control without an issue. And from what I could see there were no duplicate IDs but maybe the message was referring to duplicate entity values within the aspx vs a value with ID= that is duplicated.

Have a look at the .aspx before and after you add the control and see if you can identify what the issue might be.


paulgilfoy13
Freshman I
  • Freshman I
  • 6 replies
  • February 27, 2023

I see this stack overflow question with a similar problem.  They suggested a similar suggestion to @Django.  I’ll be diving into .aspx today. Thanks!


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