# Document Creation Logs

The **Document Creation Logs** are diagnostic records that capture what happens during purchase document creation. They are written only when logging is enabled in Core Setup and are used to troubleshoot how a Core document became a Business Central record.

## Purpose

When a purchase document is created from a Core document, several steps read the source data and build the record. If the result is not what you expect, these logs show the **source JSON** alongside the **actual record JSON** at each creation point, so you can pinpoint where a value came from or where it diverged.

## Enabling logging

- Open **Core Setup**.
- Switch on **Enable Logging**.
- Re-run the document creation you want to diagnose so that logs are written.

<p class="callout warning">Logging adds overhead and produces data at every creation point. Enable it only while investigating an issue, and switch it off again afterward.</p>

## Reading the logs

Open the **Document Creation Logs** list from Core Setup (**Document Creation Logs** action) or by searching for the page. Each entry corresponds to a creation point during document creation.

{add screenshot of Document Creation Logs here}

To compare the data, open the **JSON Comparison** view. It shows the **source JSON** (what the document provided) next to the **record JSON** (what was written to the Business Central record) so you can spot differences directly.

{add screenshot of JSON Comparison here}

## Troubleshooting workflow

- Enable logging in Core Setup.
- Reproduce the document creation.
- Open Document Creation Logs and find the entries for that document.
- Use the JSON Comparison to check where a field value was set, changed, or missing.
- Adjust field mappings or rules as needed, then disable logging.

## Related features

- Core Setup
- Field Mapping
- Core Documents