Magento Open Source 2.2.x
Data Validation

All data must pass validation before it can be imported into the store, to ensure that the values are consistent with the system database. Validation begins when you tap the Check Data button. During the process, all entities in the import file are verified for the following:

  • Attributes

    Column header names are verified to ensure that they match the corresponding attributes in the system database. The value of each attribute is checked to ensure that it meets the requirements of the data type (decimal, integer, varchar, text, and datetime)

    Complex Data

    Values that originate from a defined set, such as a drop-down or multiple select input type, are verified to ensure that the values exist in the defined set.

    Service Data

    The values in service data columns are verified to ensure that the properties or complex dataData that is associated with multiple product options. values are consistent with what is already defined in the system database.

    Required Values

    For new entities, the presence of required attribute values in the file is checked. For existing entities, there is no need to re-check the existence of required attribute values.

    Separators

    Although the separators aren’t visible when viewed in a spreadsheet, data values in a CSV file are separated by comma, and text values are enclosed in double-quotes. During the validation process, the separators are verified, and each set of quotes that enclose character strings is verified to be formatted correctly.

The results of the validation appear in the Validation Results section, and include the following information:

  • The number of entities checked
  • The number of invalid rows
  • The number of errors found

If the data is valid, an “Import Success” message appears.


File is Valid!

If validation fails, read the description of each error, and correct the problem in the CSVComma Separated Values: A type of file used to store data values which are separated from each other by commas. file. For example, if a row contains an invalid SKUStock Keeping Unit: A number or code assigned to a product to identify the product, options, price, and manufacturer., the import process stops, and that row, and all subsequent rows are not imported. After correctly the problem, import the data again. If many errors are encountered, it might take several attempts to pass validation.

  • Data Validation Messages

    mESSAgEs

    Data Validation

    Errors

    • Wrong field type. Type in the imported file %decimal%, expected type is %text%.
    • Value is not allowed. Attribute value does not exist in the system.
    • Field %column name% is required.
    • Wrong value separator is used.
    • Wrong encoding used. Supported character encoding is UTF-8 and Windows-1252.
    • Imported file does not contain SKU field.
    • SKU does not exist in the system.
    • Column name %column name% is invalid. Should start with a letter. Alphanumeric.
    • Imported file does not contain a header.
    • %website name% website does not exist in the system.
    • %storeview name% storeview does not exist in the system.
    • Imported attributeA characteristic or property of a product; anything that describes a product. Examples of product attributes include color, size, weight, and price. %attribute name% does not exist in the system.
    • Imported resource (image) could not be downloaded from external resource due to timeout or access permissions.
    • Imported resource (image) does not exist in the local media storageA dedicated space on the content delivery network for your store's assets..
    • Product creation error displayed to the user equal to the one seen during manual product save.
    • Advanced Price creation error displayed to the user equal to the one seen during the manual product save.
    • Customer creation error displayed to the user equal to the one seen during the manual customer save.