Hemi UI / Hemi 3 0 UI - Functional Scope and Wireframes / Imports / Create New Edit View Manual Import / Manual Import Step 3 MAPPING

Manual Import Step 3 MAPPING

When we are doing the mapping we want to check if there are already existing layouts related to the file because brand new file with the same headers should result in already existing layout as well. So we do not want to do the same mapping over and over again if we have already existing mapping for the file and which we want to display in the “Select layout” dropdown field.

If we select an existing mapping we want to load the actual fields mapping below which the user wont be able to edit as well as the “Has header Row” checkbox.

The user will have also the option to create a new mapping for the file which option will be available from the dropdown list “select layout” at first position. If we are creating new layout we want to show the field “Layout Name”.

If the import type is - Order, Refund, Shipping or Acknowledge we should also visualise the Prefix/Suffix options

Field Name Field Type Field Values Required Comment
1 Select mapping Dropdown All layouts applicable for this file and “create new layout” option Yes
3 Has Header Row Checkbox 1.Yes
2.No (by default) No If this is selected we know if we should ignore the first row of the file which should also update the File Header Title value
4 Select Field From dropdown Dropdown All available fields which we can map No Please note we want to add an indication in the actual dropdown which fields are required.
5 Select field from view Button No Clicking on the button will open a pop up with the actual fields and tables which we can use for the mapping.
6 Layout name Text field Yes Visible only when creating new layout.
7 Remove Prefix Text field No Visible only for imports with type

Order Shipping Refund Acknowledge | | | Remove Suffix | Text field | | No | Visible only for imports with type Order Shipping Refund Acknowledge |

Select Field From dropdown:

In the dropdown field we would like to display all available fields for the mapping but also we would like to have better distinguish between the different tables so we can add an indent before each label also we would like to add an indication which fields are required in the actual dropdown. There should be the capability of search fields by typing the label in the search bar of the dropdown while the search should work as LIKE and if the word or letters are part of any of the labels to be added in the list. We would like to have the automatic mapped fields if we have the same name between the File Header Title and our field label. Also we would like to introduce a suggestion logic which will work based on previous mappings for example if we have a layout where the header title “Product Full Title” is mapped to our Product Account > Title we would like to map it again the same way.

If we have case where the name of the file header is the same as the field label and also we have previous mapping for the field which is different we would like to use the first mapping and map with the exact same label. For example we have header title “EAN” which has been already mapped in another layout to Product Account > Marketplace EAN we want to map the header title to our Product > EAN

We would like to have a validation and if a field is already mapped to make it unavailable for mapping this way the user wont be able to map the SKU twice for example, of course there will be fields which we will allow multiple mapping to be made. For ease we can agree that all field type like Item Specifics and More Picture URLs can be mapped more than once.

Select field from view:

The “select from view” pop up will simply represent the tables (tabs) and the available fields from each table and by selecting the field we are doing the actual mapping if confirmed by the button. Here we also want to make indication which fields are required for the selected import type.

If not all required fields are mapped we want to return and error for example:

Everything is mapped correctly -

Mandatory fields are missing from the mapping -

Is this article helpful?
0 0 0