# signnow template drops fields when sent: how to fix it

Fields go missing when the template references a role that was renamed or deleted, leaving fields unmapped. Open the template in the editor, assign every orphaned field to a live role, and test-send to yourself.

```text
signnow template drops fields when sent
```

## When to use this skill
- Fields present in the template are missing from the sent document
- Fields map to the wrong signer

## When not to use this skill
- Signer leaves fields blank (a signer behavior issue)
- Fields appear but in the wrong order (a layout issue)

## Tool compatibility
SignNow template fields and roles. Related area: business integrations.

Related area: proposal automation and agent-assisted RFP workflows.

Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with fields present in the template are missing from the sent document, start at step 1 below.
- If instead signer leaves fields blank (a signer behavior issue), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Open the template field list

```
Open the template and list every field with its assigned role.
```
Expected: Expected: some fields show an unassigned or deleted role.

### 2. Reassign orphaned fields

```
Assign each orphaned field to the correct current role.
```
Expected: Expected: zero fields remain unassigned.

### 3. Test send to yourself

```
Send a test copy of the document to your own email.
```
Expected: Expected: every field appears in the test document.

### 4. Send the real document

```
Send to the real signer after the test passes.
```
Expected: Expected: signer sees the complete field set.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (open the template field list): Expected: expected: some fields show an unassigned or deleted role.
- Step 2 (reassign orphaned fields): Expected: expected: zero fields remain unassigned.
- Step 3 (test send to yourself): Expected: expected: every field appears in the test document.
- Step 4 (send the real document): Expected: expected: signer sees the complete field set.

## Quick recap
1. Open the template field list
2. Reassign orphaned fields
3. Test send to yourself
4. Send the real document

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### signnow template fields missing
Reassign orphaned fields. If this matches what you saw, the steps above apply as written.

### signnow field mapping error
Deleted roles orphan fields. If this matches what you saw, the steps above apply as written.

## Why it happens
Templates store field-to-role bindings, and renaming a role breaks the binding while the field silently drops. The template preview still shows the field, so the loss only surfaces on the sent document.

## Edge cases
- Renaming roles after building templates is the usual cause; freeze role names first
- Conditional fields can look missing when their condition is unmet; check the logic before remapping
- A test send to yourself costs nothing and catches this before the client sees it

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_dgjwpxfNuQ09L0e-5Aih-A