Overview
Data mapping is a key aspect of any system integration. In Flxpoint, mapping is handled in three ways:
- Mapping templates
- Mapping sets
- Mapping rules
| Dropdowns |
|
Mapping Templates
Mapping templates are primarily used to map external fields into Flxpoint's internal fields. These are also used for internal building processes, such as creating products.
Mapping Sets
Mapping sets are a component contained within mapping templates. These sets allow simple look-ups to occur and map a value seen into a known value within the integration, such as "A" into "Alpha."
| Use Case: |
|
You may have a "Condition" field in a listing in Flxpoint, with values "new" and "refurbished." In another system, "new" may be represented with "1" and "refurbished" may be "2." Using a mapping set similar to : → "new" → "1" → "refurbished" → "2" This will accommodate this mapping for a specific field, within a mapping template. While this may not be incredibly useful for only two values being mapped, as the subset of data needing mapped grows, mapping sets become a more valuable tool. |
Mapping Sets can then be applied in a Mapping Template for a specific field.
Mapping Rules
Mapping rules are a component contained within mapping templates. These rules allow for conditional modifications to a specific field within a mapping template.
| Use Case: |
|
Perhaps you want to clean up titles as they are imported from a source for a specific brand. One way to achieve this would be to create a mapping rule during the Get Inventory [Primary] process. This rule could be structured as : → "If Brand = XYZ" then apply "Sentence Case" to title |
Mapping Rules can then be applied in a Mapping Template for a specific field.
