Error during create package one step

Hi there, Would you be able to share your code for the package creation? More specifically, I would like to see your DocumentPackage object if possible.

Hey Haris, here is the requested json. https://jsoncompare.com/#!/simple/id=68c66de002a7954ce9da19941ff50408&reformat=beautify_2/ Please take a look.

Is that the payload that the SDK builds? Normally, the fields shouldn't be capitalized and it should be "approvals" instead of "signatures" (few ones that I spotted quickly). Here's an example payload that the SDK normally builds:

{
  "autocomplete": true,
  "data": {
    "sdk": ".NET v11.5"
  },
  "description": "",
  "documents": [
    {
      "approvals": [
        {
          "fields": [
            {
              "extract": false,
              "height": 50,
              "left": 100,
              "page": 0,
              "subtype": "FULLNAME",
              "top": 100,
              "type": "SIGNATURE",
              "width": 200
            }
          ],
          "role": "signer1"
        },
        {
          "fields": [
            {
              "extract": false,
              "height": 50,
              "left": 100,
              "page": 0,
              "subtype": "FULLNAME",
              "top": 200,
              "type": "SIGNATURE",
              "width": 200
            }
          ],
          "role": "signer2"
        }
      ],
      "data": {},
      "extract": false,
      "fields": [],
      "index": 0,
      "name": "sample doc",
      "pages": []
    }
  ],
  "emailMessage": "",
  "messages": [],
  "name": "designer test",
  "roles": [
    {
      "attachmentRequirements": [],
      "id": "signer1",
      "index": 0,
      "locked": false,
      "name": "signer1",
      "reassign": false,
      "signers": [
        {
          "auth": {
            "challenges": [],
            "scheme": "NONE"
          },
          "email": "[email protected]",
          "firstName": "John",
          "lastName": "Smith",
          "professionalIdentityFields": [],
          "specialTypes": [],
          "userCustomFields": []
        }
      ],
      "specialTypes": []
    },
    {
      "attachmentRequirements": [],
      "id": "signer2",
      "index": 0,
      "locked": false,
      "name": "signer2",
      "reassign": false,
      "signers": [
        {
          "auth": {
            "challenges": [],
            "scheme": "NONE"
          },
          "email": "[email protected]",
          "firstName": "Patty",
          "lastName": "Galant",
          "professionalIdentityFields": [],
          "specialTypes": [],
          "userCustomFields": []
        }
      ],
      "specialTypes": []
    }
  ],
  "trashed": false,
  "type": "PACKAGE",
  "visibility": "ACCOUNT"
}

Hi Haris, Thank you We have a situation where we need to move a document in one package to another, and i was directly adding document object from previous package to new one saying .WithDocument(..) during new package build. The api is not happy if i directly add a document like that from another package. I had to regenerate the document again like how i did for the existing package that document resides in. And it worked. Do you have any idea why this happens ?

Can you elaborate on "move a document in one package to another"? What is it you're trying to accomplish?

This situation comes as part of a scenario where a transaction with 5 documents and 2 signers, the Sender himself and Signer A. Signer A is supposed to visit the package sender to electronically sign, in front of him and will not receive a notification to sign at a remote place (this is a business requirement). A signs documents and leaves place after which Sender had a couple more documents to sign (these are usually ancillary, could be signed and accessed from any remote location). In this scenario we had to 'move' documents from the existing package to a new package and send the signer a notification to sign at his location. Note: 1. The place of origination of document for any signer is not completely in our control. It ends up adding document to existing package already created. 2. The documents already signed contains documents that should 'not' be shown to the signer as per the requirement. Hope it helps. Let me know if you have way to make this process easier.

Here are some suggestions I can make: 1. You can use the Document Visibility feature (https://developer.esignlive.com/guides/feature-guides/document-visibility/) to control which documents are visible to signers. 2. If all you're looking to do is send the package once the signer needs to sign at his location, then you don't need to "move" the documents and create a new package. You can simply send a notification to the signer to sign again: eslClient.PackageService.NotifySigner( packageId, email1, "HELLO SIGNER" );