Data Table Validation

Overview

You can validate Table Data by mapping Commerce and/or Configuration attributes to a Data Table column. When you add this functionality, the validation will determine if the Table Data is valid or invalid. Column data must match one menu value in the linked attribute.

Administration

ClosedSetting Up Data Table Validation

  1. ClosedNavigate to the Data Table Administration page.

    1. Click Admin to go to the Admin Home Page.

    2. Click Data Tables in the Developer Tools section.

      The  Data Table Administration page opens.

  2. Select a table and click the Schema tab.
  3. Verify the column information is correct (if legacy) or add columns.

  4. Select a Validation Type and Validation Mapping for each row in the schema.

    Data table with validation

  • Validation Type 
    • None: Select if you do not wish to perform a validation on this column.
    • Commerce Attribute: Select if mapping to a Commerce menu attribute.
    • Configuration Attribute: Select if mapping to a Configuration menu attribute.
  • Validation Mapping
    • If validation type is 'None', this field will be unavailable for mapping.
    • If validation type is 'Commerce Attribute', select from main-document or sub-document menu attributes.

    • If validation type is 'Configuration Attribute', select from Configuration menu attributes in the product hierarchy.

Integer and float multi-select menus can be used in a validation, but only a single value can be selected. Saving schema might take a long time if a column is mapped, or will be mapped, to a multi-select menu attribute.

  1. Click Save to save your changes.

    For legacy data, you can add and save the validation, but you will get an error message that instructs you to remove the invalid data before you can deploy the Data Table.

ClosedValidating Against Both Menu Attributes

If you are migrating a Data Table that has a commerce menu attribute validating one column and a configuration attribute validating another column:

  • Performance is acceptable, but there will be a decrease in performance on both the import and the UI if large Data Tables are being uploaded.
  • The indication in the logs will be the record number in the .CSV file.

Another option is to remove either the commerce or the configuration validation, migrate the Data Table, and then add the validation back to the migrated table.

Troubleshooting

If you are adding a validation to a Data Table with existing data, and invalid data is present, use the Invalid Data button to:

Import .CSV will not update existing record. but it will allow you to modify values.

To replace the table, you must clear the Data Table and upload the file. Alternatively, delete the table and upload a new one through .CSV.

Notes

Validations will run as part of bulk import. If there are records that do not meet the validation, then the invalid records will fail.

There is no validation of column data type with Parent Entity data type because in Commerce, there are only text type menu attributes.

Related Topics

Related Topics Link IconSee Also