Field Mapper Configuration
The field mapper maps data between the integrations you work on during the node configuration. It is used in all update nodes, including Airtable Update, Webflow CMS update, Knack update, and Infinity update.
In this documentation, we'll explain how to configure a field mapper.
How does it work?
The field mapper lets you handle the updates and inserts in the integration. It first retrieves the data from the integration through an HTTP Get call. An update request is executed for the existing data on the integration service, but if the data doesn't exist, the insert command is executed.
Add Update task to a flow
Let's assume we're configuring a field mapper for Webflow - Update Items node.
Step - 1. Select Webflow - Update Items node to configure the field mapper in the Byteline flow designer console.
Step - 2. Click on the edit button of the Webflow - Update Items node for configuration.
Let’s start field mapper configuration.
Field Mapper Configuration
In this section, we will learn to configure each of the column’s data irrespective of their collection field. Byteline populates the Field Names for which data needs to be configured. If any field is missing, you can add it using the + button.
Step - 3. Click and select the site in your Webflow account
Step - 4. Click this dropdown.
Configuring mapped expressions
Step -1. Click on the respective Selector button to fetch the array path in the Value field of the Name column.
Step - 2. Click on the variable to pick its path.
Step - 3. Toggle one or multiple fields as unique fields. These field(s) are compared to their values on the integration service, such as Webflow CMS, to determine whether we need to create or update a record. In the case of multiple unique fields, all the unique fields must match.
If you have deleted a field from the mapper, you can use the "Refresh fields" button to bring it back. You can also use it to get new fields added after configuring the task.
Click on the Collapse button to explore all the advanced options to manage your Airtable data, which includes:
- Deleted At Source (Deprecated, will be removed in a future release)
- Filter Existing Items (Deprecated, will be removed in a future release)
To manage the existing records, you can select one of the below-discussed update strategies:
- Skip Updates
- Overwrite When
Select the Skip Updates option in case you don't want any data updates on your existing records.
Select the Overwrite option to replace old items with the new data when required.
Select the Overwrite When the option to set a specific condition based on which the update should be performed.
Filtering Existing Items
Filter the records you want to consider for figuring out whether to create, update or delete records. Select the None option if you don't want to apply the filter to the records.
Select the Filter option to apply the filter to the required existing records.
In the first field, enter the column id to which you want to apply the filter.
You can choose to filter the existing items based on various parameters, including:
- Equals To
- Not Equals To
- Not Contains
Enter the Value of the column for applying the filter.
Deleted at Source
When a record has been deleted from the source data but it still exists in your integration e.g. Webflow, then you can decide how to manage it.
If you select the ignore option, no data is deleted.
Select the Set a Column Value option to set a column to a specific value for deletion. For example, you can configure to set the status column to expire.
Click on the Save button to save the configuration.
This way, you can map field values for Airtable Update, Knack update, Infinity update.
Feel free to connect us with any doubts.