# merge field error showing code instead of value: how to fix it

Merge fields showing code instead of values means the exporter treated them as literal text, usually a syntax typo or fields inserted as plain text rather than real fields. Delete the broken field and re-insert it properly from the field picker. Re-typed fields almost always carry a subtle syntax error.

```text
merge field error showing code instead of value
```

## When to use this skill
- Exported proposals show field codes instead of values
- Fields look right in the editor but export raw

## When not to use this skill
- Fields show wrong values (a mapping issue)
- Fields are blank rather than showing code (a data issue)

## Tool compatibility
Proposal generators with merge field syntax. Word and PDF exports.
Related area: document export, rendering, and OCR tooling.
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 exported proposals show field codes instead of values, start at step 1 below.
- If instead fields show wrong values (a mapping 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. Confirm they are real fields

```
Click a broken field in the editor to see if the tool recognizes it as a field object.
```
Expected: plain text means it was typed, not inserted.

### 2. Delete and re-insert from the picker

```
Remove the typed text and insert the field using the insert field menu.
```
Expected: the field appears as a proper field object.

### 3. Check the syntax against docs

```
If the picker is not available, compare your syntax character by character with the documentation.
```
Expected: a typo or wrong delimiter found.

### 4. Re-export and verify

```
Export the proposal and check the values.
```
Expected: real values where the code used to show.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (confirm they are real fields): Expected: plain text means it was typed, not inserted.
- Step 2 (delete and re-insert from the picker): Expected: the field appears as a proper field object.
- Step 3 (check the syntax against docs): Expected: a typo or wrong delimiter found.
- Step 4 (re-export and verify): Expected: real values where the code used to show.

## Quick recap
1. Confirm they are real fields
2. Delete and re-insert from the picker
3. Check the syntax against docs
4. Re-export and verify

## 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
### merge field showing code proposal
Typed fields are the cause, use the picker. If this matches what you saw, the steps above apply as written.

### field code visible in export
One wrong character in the delimiter breaks recognition. If this matches what you saw, the steps above apply as written.

## Why it happens
Exporters only resolve text the editor marked as field objects. Hand-typed field syntax looks identical to you but is plain text to the exporter, so it passes through unresolved.

## Edge cases
- Copy-pasting fields between documents can strip the field object status
- Some tools need a refresh after inserting fields before export
- Field pickers vary by template, check you are in the right one

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_P5NPLizu3UmZtWXHCOyTDA
