mbilensky's account

Thanks! This is just what I needed

Having an issue using the above code for one specific layout. While this code has been working most of the time I ran into an issue when attempting to create a copy of one specific layout. An exception keeps being thrown stating that there are multiple entries with the same key for a field. I’ve looked through the properties of the layout and found a text field for a signature that has the id that the exception states there are multiple entries for, but no other fields with the same id. The same call is being done with identical layouts without any exceptions being thrown and is working as intended. I’ve been unable to recreate the issue outside of this one specific layout and wondering if you could provide any further information that could help. Approximate Code being used:

String layoutId = “NljTbsDDTYygDj6vXvMzN3Kszio=”
DocumentPackage layout = eslClient.getPackage(new PackageId(layoutId));
layout.setName(layout.getName() + “-1”);
String clonedLayoutId = eslClient.getLayoutService().createLayout(layout);
layout = eslClient.getPackage(new PackageId(clonedLayoutId));

Exception being thrown:

Caused by: com.silanis.esl.sdk.internal.EslServerException: Could not create layout. Exception: HTTP POST on URI https://sandbox.esignlive.com/api/layouts resulted in response with status code: [500, Internal Server Error]. Optional details: {"messageKey":"error.internal.default","technical":"Multiple entries with same key: MF84tvhX2NsV=com.silanis.esl.api.model.Field@31a655ed and MF84tvhX2NsV=com.silanis.esl.api.model.Field@18c0f02f","code":500,"message":"Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team.","name":"Unhandled Server Error"}
	at com.silanis.esl.sdk.service.LayoutService.createLayout(LayoutService.java:55)

I can provide the API Key and layout id being used if needed Thanks in advance, Mitch

That looks whats causing the issue, but I'm now more concerned on how the layout got into this state in the first place. Is this a case of id collision? Is there any way to protect against this in the future or is this just a random chance event?

This layout specifically was cloned using the same code as above and then had the layout designer window opened where the fields were added, and the original layout was created using this workflow except for adding placeholders instead of signers and adding signatures through the layout designer window instead of being added through the sdk.

Thanks! I knew it had to be in draft mode, but was unsure about altering the partially signed documents. Is there a supported way to complete a package after one of the signers has Declined or Opted-Out of a partially signed package? Or will the package always remain Declined/Opted-Out? Thanks again, Mitch