> This page is for Docs.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Field Mapping Page Layout

> The Field Mapping page provides navigation and management of mappings, highlighting actions, search, child objects, and partitioned objects.

The Field Mapping page provides navigation and management of mappings, highlighting actions, search, child objects, and partitioned objects.

The **Field Mapping** page contains several components that allow users to navigate and manage mappings.

The page highlights the following main concepts:

* Actions
* Search
* Child Objects
* Partitioned Objects

  ![Concept layout](/_fern-img/b0d04e5ef3f20e2a7322cc64234b631e84c77a9303e8e173c09bd62ad15ba4f4.webp)

## Actions

The **Actions** section is located at the top of the page. These actions allow users to adjust and test field mappings.

Additional details about the available actions are described in the [Field Mapping Actions](/docs/platform/integration/integration-hub/get-started-with-integration-hub/field-mapping-tools-overview/field-mapping-actions) topic.

## Search

The **Search** bar is located above the list of fields and applies to all objects and fields.

It allows users to quickly locate specific fields and mappings across objects.

## Child Objects

Child objects represent objects that are related to a parent object through inheritance.

A child object originates from the parent object and has access to the data available at the parent level.

For example, Invoice Items are child objects of Invoices. Because of this relationship, Invoice Items can access Invoice data in their field mappings.

## Partitioned Objects

Partitioned objects occur when different parent objects map to the same target object but require different mappings.

For example, Zuora Invoice, Credit Memo, and Debit Memo all map to SAP Billing Documents.

This relationship can be found in the corresponding SAP capability configuration.

![Partitioned Objects Example](/_fern-img/32d89fa986304f5e9579bae8d8d0033e216880d68ec331abd58ddcc05b42ef5c.webp)

## Field Mapping Actions

Editing

The **Editing** action unlocks the field mapping interface so that users can modify mappings.

After making changes, click **Save** to apply the updates.

Dry Run

The Dry Run action executes a test job using the current field mappings. This job retrieves data from the source system and simulates a synchronization process. The job runs similarly to a normal synchronization job and its results appear in the **Jobs** tab.

However, no data is sent to the target system. Instead, the job output displays a sample payload so that users can validate their mapping configuration. Ensure that you save all mapping changes before executing a dry run.

## Edit Field Mapping

Correctly mapping data between systems is essential for connector operations.

The **Field Mapping** page provides tools that allow users to locate source fields, configure mappings, and transform data during synchronization.

To begin modifying mappings, click **Edit Mapping** in the top-right corner of the page.