Troubleshoot QCDS Builder Validation and Field-Placement Problems

When QCDS refuses to validate a Template or a Request, start with the exact message instead of moving fields or changing assignments at random. Template validation checks reusable document structure; Request Check adds transaction-specific assignment and Request Text requirements.

First Identify Which Validation Is Failing

  • Template Validate: checks the reusable PDF, pages, field definitions, geometry, roles, links, options, variables, and other publishable structure.
  • Request Check: checks the current transaction and requires the interactive fields to resolve to actual signers plus all Request Text values to be supplied.

A reusable Template may intentionally leave interactive fields without a concrete Contact assignment. That becomes a blocking issue only when the Request is being prepared for Send Now.

Fix Document and Page Problems

  • The Template must contain at least one ready canonical PDF.
  • Every builder item must point to an available document and page.
  • If page preparation or metadata is incomplete, correct the PDF/document readiness problem before adjusting field settings.

When the failure appears tied to one complex PDF, reproduce the workflow with a small known-good PDF. If the simple PDF works, investigate the source document rather than rebuilding unrelated QCDS settings.

Fix Field Placement and Size

QCDS stores field geometry relative to the PDF page. A field or asset that extends beyond the page is a blocking error. Very small fields produce a warning because they may be difficult to use accessibly. Substantial same-layer overlap can also produce a warning.

Select the affected item, move or resize it fully inside the page, then Validate again.

Fix Field-Definition Problems

  • Every field needs a visible label or accessibility name.
  • Document Text must contain text before Template publication.
  • A Dropdown needs at least two non-empty authored options.
  • Retired/unsupported field types must be replaced with current field types.
  • Signed Date must link to an available Signature or Initials field and remain read-only; assignment mismatches are rejected.
  • Unknown variables, invalid rules, broken links, or unavailable assets/documents must be corrected rather than ignored.

Fix Request-Specific Problems

After choosing Use on a published Template, open Prepare & Send and run Check. If QCDS reports unassigned fields, assign them to the intended signer. If it reports an empty Request Text field, enter the transaction-specific value. Do not edit the reusable Template merely to solve data that belongs to one Request.

Use the Smallest Corrective Test

  1. Correct the first concrete error reported by QCDS.
  2. Validate or Check again.
  3. Continue until no blocking errors remain.
  4. Run one controlled test Request and inspect the signer page and completed output before using the Template in production.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.