> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/data-harmonization/syntactic-mapping/syntactic-mapping-configuration.md).

# Syntactic Mapping Configuration

## Overview

This topic explains how to work with RhinoDHE **Syntactic Mapping configurations** in **JSON** format.

A [Syntactic Mapping](/data-harmonization/syntactic-mapping.md) defines how source fields map to target fields, including any [transformations](/data-harmonization/syntactic-mapping/column-transformations.md) that should be applied during the harmonization process. You can create and edit these mappings directly in the Rhino FCP UI or view, download, edit, and upload the same configuration in JSON format.

{% hint style="info" %}
The JSON format is simply an alternative representation of the Syntactic Mapping configuration and supports the same mapping and transformation capabilities available in the FCP UI.
{% endhint %}

## Prerequisites

You must have the "Manage Data Mappings" permission.

## Accessing a Syntactic Mapping Configuration

You can view a syntactic mapping configuration in JSON format, by completing the following steps.

1. In the **Syntactic Mappings** page, select the three-dot menu for the version of the syntactic mapping you want to view and select "Show configuration".
2. The **Syntactic Mapping Configuration** page appears. Scroll down to see the Mapping Configuration if it is not visible.

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/HpWiGY426GQOdcAiHvtA/23780144543773)

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/3nbW8oLLOwYOrj9AEek5/23780144544413)

If you want to **copy** the configuration mapping to your computer's clipboard, select the rectangle on the right side of the page.

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/lYIYoUohzRlHruVzfUWD/23780144544797)

3. Select **Close**.

## Downloading a Syntactic Mapping Configuration&#x20;

1. In the **Syntactic Mappings** page, click the three-dot menu for the version of the syntactic mapping you want to download and click "**Download mapping config**".
2. The configuration file downloads to your local computer.

<figure><img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2Fni0LmCEsSIeUznW6MfRY%2Fimage.png?alt=media&amp;token=087a8778-d96c-45ea-bdb2-0348b53c0f4f" alt=""><figcaption></figcaption></figure>

## Creating a Syntactic Mapping from JSON Configuration

1. In the **Syntactic Mappings** page, click the "**Create Syntactic Mapping**" button. The Create Syntactic Mapping Page appears.
2. Enter a name, optionally also a description, and select your target data model.
3. Under configuration, select "Upload From File", and then **select your JSON configuration file**.
4. Click **Create Syntactic Mapping**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rhinofcp.com/data-harmonization/syntactic-mapping/syntactic-mapping-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
