Product/Inventory Sync Data Mappings

*The following article walks you through FarApp's "advanced" methods for creating Product Mappings. These steps will use screens that normally only FarApp representatives interact with. Please see this article for creating more basic Product Mappings:  https://support.farapp.com/hc/en-us/articles/225798028-Product-Inventory-Sync-Data-Mappings-in-app-farapp-com If you need to create more sophisticated mappings, please contact FarApp support so we can assist you.

FarApp maps your data from your backend system (e.g. NetSuite) fields to each connector set up for product sync and/or inventory sync. At the most basic level, the mappings define which field in your backend system post to which field in your marketplace/cart. However, mappings can be more complex and can combine multiple fields, can adjust values according to mapping rules, can post default values, etc. Mappings are fairly powerful and can handle a lot of business logic, so please contact us if you need help setting up a complex mapping. To review/adjust your mappings, do the following:

  1. Go to the FarApp Product Mapper here: https://adv.farapp.com/secure_QuickMapper.

  2. Switch to the correct category you want to review/adjust at the bottom of the screen.
    1. For eBay, your standalone items use the eBayFixedPrice category. If you also post variation items to eBay, you'll find the mappings in the eBayVariations category.
    2. For Amazon, you'll usually have an "Amazon" category which will contain the majority of the mappings. Then each individual Amazon category you post items to will have its own individual category. If all of your specific categories have a mapping in common, it only needs to be set up in the "Amazon" category. If you want to override one of the mappings for only a subset of your Amazon categories, then the mappings will need to be defined in those individual categories.
  3. The left pane has three tabs. These are details below:
    1. Client (Source) Fields: These are the fields that we can map from your backend system (e.g. NetSuite). They can only go in the "Client Field" column in the middle pane or (for certain mapping rules) in the "Rule Args" column. FarApp has a specific format it uses so any field you can map will be found here. Any mapping you create that contains a source field must match the text exactly as it shows in this tab. Otherwise, it won't match the format that FarApp uses and won't work. Double-clicking on a client field in the left pane will pop up a window showing some sample values that have been loaded for that field. You can also drag the field to the yellow section of a mapping in the middle pane and it will automatically populate in the "Client Field" column of the corresponding mapping.
    2. Rules: These are the mapping rules that have been defined in FarApp to create more complex mappings. They can only go in the "Mapping Rule" column in the middle pane. If you single-click a mapping rule, it will show a description of the rule at the bottom of the page. If you double-click a mapping rule, it will pop up a window showing how the rule has been used in other mappings for comparison. You can also drag the rule to the yellow section of a mapping in the middle pane and it will automatically populate in the "Mapping Rule" column of the corresponding mapping.
    3. Storefront (Target) Fields: These are the available fields in the category you're currently mapping. Double-clicking a field will create a new mapping rule in the middle pane with that field in the "Storefront Field" table. If you do this, make sure you complete the mapping for that row or if it was accidentally created, make sure you delete the mapping. Incomplete mappings will cause an error for the FarApp product/inventory sync processes. You can also drag the field to the yellow section of a mapping in the middle pane and it will automatically populate in the "Storefront Field" column of the corresponding mapping.
  4. The middle pane has all of your mappings for the selected category. These are the details of the columns:
    1. Storefront Field (required): This column is the field in the marketplace/cart that is being mapped to.
    2. Seq (required): This field has no effect between mappings for different "Storefront Field" values and should have the value "0" (i.e. zero) or "10". However, if you have multiple mapping rows for a single "Storefront Field" the value in this column determines the order in which the mappings run in increasing order so you'll often see increasing increments of "10" to define the order of mappings.
    3. Client Field (optional): This is a field from your backend system (e.g. NetSuite). The text has to match exactly one of the values in the "Client (Source) Fields" tab. If this isn't the first mapping for this target field (according to the Seq) value or if the target field is being populated using a value in the "Default Value" or "Mapping Rule" columns, then this field doesn't have to be populated.
    4. Default Value (optional): This is the value to set the Storefront Field to if the other columns in the mapping row haven't been set and/or don't produce any output (e.g. you populated a Client Field but you didn't put a value in the field in your backend system).
    5. Mapping Rule (optional): You can use a rule from the Rules tab to create more complex mappings. For example, if you're mapping a list field from NetSuite, you must use the NSListValue mapping rule to output the value instead of the ID of the selected list item in NetSuite.
    6. Rule Args (optional): The arguments required for a specific rule. These are typically space-separated. If you want to provide an argument that has spaces or a blank argument, please enclose the value in backticks (i.e. a blank argument would be ``).
    7. Account (required): If this mapping should apply to all of your accounts using this connector, the Account value should be "*". Otherwise, set the Account value to the matching account name. If you want a particular mapping to only apply to a subset of accounts, you'll want to clone the mapping row for each account and set the Account value appropriately.
    8. To Children? (optional): This is useful for variation items (e.g. Matrix items in NetSuite). If you want a mapping to use a parent's value for a field, then check this field.
  5. After making modifications, please click "Save Changes" at the top to commit your changes.


  6. This is the explanation for the buttons at the top of the middle pane:
    1. Refresh (not typically used): This will delete all of your changes and will reload your mappings from FarApp.
    2. Add Missing Destination Fields (not typically used): This will add all available "Storefront Field" values to the middle pane as mappings. If you click this, once you're done mapping, make sure there are no mapping rows in the middle pane that have a "Storefront Field" value with no other columns populated or this will cause an error.
    3. Delete Unmapped Fields (not typically used): This will delete any mapping rows that have value in the "Storefront Field" column but no other column populated (i.e. they haven't been mapped).
    4. Save Changes: Commit any mapping changes so they're saved permanently.
    5. Cancel Changes (not typically used): Revert any of the changes you've made since the last save.
    6. Sort: This will sort by Storefront Field and Seq in ascending order just for display purposes and ease of mapping since this will display the rows in mapping order.
    7. Remove: Clicking this button will delete the currently selected mapping. You'll need to click on a mapping row to select it.
    8. Clone: Clicking this button will duplicate the currently selected mapping. You'll need to click on a mapping row to select it.
    9. Propagate (not typically used): This will copy the currently selected mapping to all related categories (e.g. if you're editing the eBayFixedPrice category, it will copy the mapping to the eBayVariation category). You'll need to click on a mapping row to select it.
    10. Compare: This will show other mappings utilizing the currently selected mapping "Storefront Field" value. Seeing how they've been mapped in other cases helps substantially with mapping.
    11. Display (not used): Use at your own risk.
    12. Restrict (not used): Use at your own risk.

Comments