# merge field date format wrong in exported proposal: how to fix it

Date fields merge as raw serial values or system-locale formats unless formatted. Apply an explicit date format to the merge field in the template, then re-export.

```text
merge field date format wrong in exported proposal
```

## When to use this skill
- Dates export as numbers like 45658
- Dates export in the wrong locale format

## When not to use this skill
- Dates show the wrong day entirely (a data issue)
- Date fields are blank (a missing-data issue)

## Tool compatibility
Merge field date formatting. Related area: document processing.

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 dates export as numbers like 45658, start at step 1 below.
- If instead dates show the wrong day entirely (a data 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. Find the date merge fields

```
List every merge field in the template that renders a date.
```
Expected: Expected: all date fields identified.

### 2. Apply an explicit date format

```
Set the field format to the required pattern, for example day month year.
```
Expected: Expected: field properties show the explicit format.

### 3. Preview the merge

```
Run a merge preview on one record.
```
Expected: Expected: dates render in the required format.

### 4. Export the full proposal

```
Export after the preview is correct.
```
Expected: Expected: every date in the export matches the required format.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (find the date merge fields): Expected: expected: all date fields identified.
- Step 2 (apply an explicit date format): Expected: expected: field properties show the explicit format.
- Step 3 (preview the merge): Expected: expected: dates render in the required format.
- Step 4 (export the full proposal): Expected: expected: every date in the export matches the required format.

## Quick recap
1. Find the date merge fields
2. Apply an explicit date format
3. Preview the merge
4. Export the full proposal

## 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 date format wrong
Explicit format on the field fixes it. If this matches what you saw, the steps above apply as written.

### proposal date format merge error
Format the field, not the source. If this matches what you saw, the steps above apply as written.

## Why it happens
Merge engines pass the raw date value through unless the field carries a format instruction, so the export inherits whatever the system locale produces. Previewing one record catches it before the full export.

## Edge cases
- Decide the date format with the client up front; it varies by region
- Source dates as text never reformat; keep them as real dates in the source
- Checklist the date fields after every template change

## Provenance

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