If you go to "Setup > Edit Mapping", you will get a screen that's similar to the one below. On the left side, you have the "Import fields", which are the fields that Channable found in your import feed or import webshop connection. On the right side, you have the "Project fields", where you can set the name for the Import fields as soon as they enter Channable.
This is the list of fields that can be used elsewhere in the project (e.g. in rules, API settings, attributes, etc.). They have a fixed type (such as "Number", "Text", etc.) and you can choose whether the field is
supposed to be just a single value, or multiple values (such as additional_image_links). Channable will automatically map your imported fields to standard internal fields, and will set their types. If one or both do not match, you are free to change the field name and type by clicking on the project field type.
Tip! Click on the image.
If the field does not match your import, you can customize the field. You can do this by choosing another standard Channable field from the dropdown or by clicking on the type next to the field. Here you will see a screen where you can change the name, the type of field, and whether the field consists of a list of multiple values, by clicking on the checkbox.
The types you can choose are:
- Date and time
Make sure you check the type of the field, as it affects how we treat the value in the field and how you can further edit the information in the tool in, for example, the rules. When you have a field with a date in it, but in the import mapping the type is set to 'Text', you cannot use this field in the date rules because Channable does not see it as a date due to the type that is selected.
* Tip! When you want to create nested fields, then choose the field type 'Object'. After you have done this, you can create sub-fields:
Project fields overview
This is also the place where extra fields (that are only used in rules, but not imported from anywhere) need to be added. Read this article for more information about adding new fields in the project fields overview.
What is the difference between a standard field and a custom field in the import mapping?
The standard fields in Channable are the most common fields used in imports and exports, like the price or brand. Some of the standard fields have special properties. For example, the 'ean' and 'gtin' standard fields have an option to be validated in a rule, but are limited in applying other kinds of rules. The date fields also have specific date rule options.
Other than the special properties, there is no difference in custom or standard fields. Channable will automatically map your imported fields to standard internal fields if they match, but you are free to make it another project field if you want to change the internal Channable field name.
When will the fields I mapped in my import be automatically mapped to fields in an export Feed or API?
Your internal fields, as mapped in your import mapping, will be automatically mapped to fields in an export channel (i.e. the Finalize step of a Feed, or the Build step of an API) when they are named the same. So, for example, your 'price' field is automatically mapped to the Price field of an API in the Build step. If the name doesn't match, such as having a field called 'stock_quantity' instead of 'stock', you will probably need to map this field to the Stock field in the Build step manually.