# Configure Field Mappings ## What it is Field mappings connect a field in your external system to the corresponding field in NetSuite. When a flow runs, it uses these mappings to know where to put each piece of data. For example, a mapping might tell IDC to put the order's customer email into the **Email** field on the NetSuite sales order. ## When you'd use it Use this when you need to: * Add a mapping so a field from your external system is written to a specific NetSuite field. * Remove a mapping for a field you don't want IDC to sync. * Update a mapping if a field name has changed in your external system. ## Before you start * You need integration admin access. * The app must already be installed and configured. See [Apps & Marketplace](/idc/idc-core/apps.md). * Most flows come with pre-configured mappings that work out of the box. Only add or change mappings if you have a specific reason — modifying pre-configured mappings can cause sync failures if the fields don't match. {% hint style="warning" %} Some mappings are locked and can't be edited — these are required for the flow to function correctly. If you need to change a locked mapping, contact In8Sync support. {% endhint %} ## Step by step ### View the mappings for a flow 1. Click **Apps** in the left menu. 2. Find the app and click its **gear icon** to open the app's management view. 3. Find the flow you want to inspect and click its **Configure** button, then scroll to the **Mappings** section. ![The Mappings section showing the field mapping table with NetSuite Field, External Field, Fixed Value, and Priority columns](/files/iLkFugIrI7VHSWU1OMTt) 4. The table shows each mapping as a row. The key columns are **NetSuite Field** (the field in NetSuite) and **External Field** (the field in your external system). You'll also see **Fixed Value** (a static value to use instead of a mapped field) and **Priority** (the order in which fields are applied). Read across each row to see how they correspond. ### Add a new mapping 5. Click **Add Mapping** at the bottom of the Mappings section. 6. In the **NetSuite Field** column, type or select the NetSuite field you want to write to. 7. In the **External Field** column, type the name of the field from your external system exactly as it appears in the data. ![A new mapping row with the NetSuite Field and External Field inputs ready to fill in](/files/lrNZihASn6QbqYPk3GMy) 8. Click **Save Mappings** to save. The mapping will be used on the next sync run. ### Edit an existing mapping 9. Find the mapping you want to change. The **NetSuite Field** and **External Field** columns are editable text boxes — click directly into the one you want to update and type your change. You can also click the button next to either field to browse and select from the available fields. 10. Click **Save Mappings** to apply your changes. {% hint style="info" %} For advanced options — such as setting a source field ID, a script, or conditional logic — click the **Edit Mapping** button on the row. These fields are rarely needed for standard field name edits. {% endhint %} ### Remove a mapping 12. Find the mapping you want to remove and click the **Delete Mapping** button on that row. The mapping is removed immediately from the table. 13. Click **Save Mappings** to confirm the removal. ### Restore default mappings If you've made changes and want to start over, click **Predefined Mappings** at the bottom of the Mappings section. This restores the flow's original out-of-the-box mappings. {% hint style="warning" %} Restoring predefined mappings will remove any custom mappings you've added. Only do this if you want to reset to the defaults. {% endhint %} ## What success looks like * The Mappings table shows your new or updated mapping. * After the next sync run, the mapped field appears correctly on the NetSuite record. Check [Logs](/idc/idc-core/logs.md) to confirm the run completed. ## Common issues * **A new mapping isn't writing data to NetSuite.** Confirm that the external field name is typed exactly as it appears in your external system's data — including capitalisation and any dots or underscores. Check [Logs](/idc/idc-core/logs.md) and look at the request details for an example of the actual field names. * **After adding a mapping, records are failing that worked before.** The NetSuite field name may be wrong. Open the log entry for a failed record and read the error message for clues. Remove or correct the mapping and reprocess. * **A row's text fields are greyed out and can't be edited.** The mapping is locked — it's required for the flow to work. The **Delete Mapping** button is also hidden on locked rows. Contact In8Sync support if you need to change a locked mapping. ## Related * [Understanding Flows](/idc/idc-core/apps/understanding-flows.md) — how flows and their tabs work. * [Configure a Flow](/idc/idc-core/apps/configure-flow.md) — adjust a flow's options alongside its mappings. * [Configure Triggers](/idc/idc-core/apps/triggers.md) — control when the flow runs. * [Logs](/idc/idc-core/logs.md) — check whether mappings are working correctly after a sync. --- # Agent Instructions: 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: ``` GET https://docs.in8sync.com/idc/idc-core/apps/field-mappings.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.