Warnings highlight a cell in yellow (unlike red for Errors) and show the end-user a message. They can be created by validation code hooks or validation webhooks. In the Importer product, Warnings can also show a suggestion (or an array of suggestions).

Importer

When receiving the imported data from OneSchema, the default behavior for Warnings is that warning rows are considered error rows. In the JSON result you receive from OneSchema, Warnings will be in error_records, not in records. This can be configured in Customizations:

This customization solely controls how rows with only warnings appear in a JSON import. CSV and Excel output file formats are not affected by this setting. If you would like to generate a CSV file with clean rows and Warning rows and you have the customization to prevent users from importing in the presence of errors, you can use the Get imported file url for an embed API endpoint with row_filter set to all.

FileFeeds

The default Warning behavior in FileFeeds is treat warning rows as clean rows. This can be configured in a FileFeed’s settings, along with the customization for whether the file feed allows partial imports:

The customizations in the screenshot above will affect the imported / error row counts, the imported file, and import status.

Here's what will be affected depending on the settings you apply:

Treat warnings as clean

• Imported row count: clean rows + rows with only warnings
• Error row count: error rows
• CSV file export format contains clean + rows with only warnings
• JSON file export format contains all rows; rows with only warnings are present in the records array

A list of possible scenarios depending on Partial Import settings:

Treat warnings as errors

• Imported row count: clean rows
• Error row count: error rows + rows with only warnings
• CSV file export format contains clean rows
• JSON file export format contains all rows; rows with only warnings are present in the error_records array

A list of possible scenarios depending on Partial Import settings: