Skip to main content
Question

DocuSign Error 24R1 - ‘An item with the same key has already been added’

  • September 24, 2024
  • 10 replies
  • 188 views

meganfriesen37
Captain II
Forum|alt.badge.img+12

Our client started testing the DocuSign integration in a testing sandbox with 23.117.021 and a DocuSign developer account this summer and everything worked. Now, they are currently testing their 24.110.0017 upgrade and the DocuSign 24R1 package using their DocuSign Business Pro account. Everything is the same for them from creating the file in the Sales Order screen, moving through to File Maintenance and then ESIGN. However, now when they press send, an error appears “ An item with the same key has already been added.” After reviewing the code, it appears to be using the DocuSign API to send, and we can’t see anywhere else on the Acumatica side that could be generating the error.   Does anyone know how to resolve this error?

 

10 replies

DavidEichner
Captain II
Forum|alt.badge.img+13
  • Captain II
  • September 25, 2024

Hi @meganfriesen37 

It sounds like a bug.  Make sure to report it on the portal as a support case so that Acumatica is aware of it.  Maybe also add a product idea that they fix it?

Best,

David


meganfriesen37
Captain II
Forum|alt.badge.img+12
  • Author
  • Captain II
  • September 25, 2024

Because the DocuSign integration is a community supported integration and support/maintenance from Acumatica they don’t cover support for this through the standard partner / customer support agreement and it’s an extra charge.  

eSign Integration | Community (acumatica.com)


DavidEichner
Captain II
Forum|alt.badge.img+13
  • Captain II
  • September 25, 2024

@meganfriesen37 

Ahhh.  Understood.  You might have to identify if the code uses a DLL or has the code exposed in the customization package.  If a DLL, someone has the source code in Visual Studio somewhere.  You would have to find out who to talk to regarding required updates to the code base.

Best,

David


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • November 14, 2024

Hi @meganfriesen37 were you able to find a solution? Thank you!


meganfriesen37
Captain II
Forum|alt.badge.img+12
  • Author
  • Captain II
  • November 18, 2024

No.  It’s still not working.


  • Freshman I
  • November 28, 2024

I am having the same issue.  Please post a response here if you find a solution


jdobish
Pro III
Forum|alt.badge.img+2
  • Pro III
  • December 5, 2024

we had a client go through it when they copied their sandbox and it caused the issue. They were unable to find a solution at this time as well. 


Does anyone have a resolution for this?  I am having the same issue with a couple of my clients as well.


meganfriesen37
Captain II
Forum|alt.badge.img+12
  • Author
  • Captain II
  • December 10, 2024

@jeremyd45 - any idea if deleting the sandbox fixes the issue?  The client that started this whole chain has finished their upgrade and their upgrade sandbox just expired, but I know Acumatica doesn’t delete them instantaneously.  The DocuSign integration was failing in both the production environment (and still is) and the upgrade sandbox.


jdobish
Pro III
Forum|alt.badge.img+2
  • Pro III
  • December 10, 2024

@meganfriesen37 It did not. They ended up deciding that they were going to unpublish it and not go down the docusign path.