> ## Documentation Index
> Fetch the complete documentation index at: https://parser.xdr.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# The fields were found, but their output names are wrong

> How to change just the mapping rather than rewriting a working parser.

# Parser Studio found the values, but mapped one incorrectly

**Situation:** **Analyze Logs** succeeded. **Review Fields** shows the right source IP, user, action or port, but the field's final destination is incorrect.

## Fictional example

```json theme={null}
{"action":"blocked","client_ip":"192.0.2.44","server_ip":"198.51.100.8","server_port":"443","device_build":"9.1-demo"}
{"action":"allowed","client_ip":"192.0.2.45","server_ip":"198.51.100.9","server_port":"80","device_build":"9.1-demo"}
```

## Walkthrough

1. In **Auto Parser**, paste the logs and select **Analyze Logs**.
2. If analysis is complete, choose **Review Fields**. Confirm that the correct source values were extracted.
3. Choose **Map Fields**.
4. Under **Review field matches**, identify the source field whose destination is wrong.
5. Use **Choose Stellar field** to review a suitable supported destination, and **Value type** to choose the matching type.
6. For unclear vendor-only information such as `device_build`, keep a custom/vendor field rather than inventing an official meaning.
7. Open **Check all sample logs** and **See what will change** to inspect the corrected result.
8. If **Must fix before continuing = 0**, click **Create Parser**.

<img src="https://mintcdn.com/xdr-parser/DkeLTskQMJz9hCfD/images/04-map-fields.png?fit=max&auto=format&n=DkeLTskQMJz9hCfD&q=85&s=5488cbce49161133f781a363025b7fd2" alt="Map Fields UI with matched destinations, value types and sample checks" width="1440" height="2941" data-path="images/04-map-fields.png" />

*This is the normal place to correct a destination or type. The original log text remains unchanged.*

## Expected review outcome

The output destination matches the actual meaning of the source value on all tested events. Corrected mappings do not erase the original extracted data.

## Recovery path

If a mapping reports **two fields use the same destination**, **value type mismatch** or **reserved field**, follow the on-screen finding. If you cannot determine the meaning, keep the source under a neutral vendor field until verified.

**Next:** [Mapping explanation](/workflows/map-fields).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.