Skip to main content

Release notes (June 17)

More options for dealing with unresolved errors​

This week, we released a new configuration setting, invalidDataBehavior, to allow better control over how Dromo behaves when there is invalid data during the Review step.

As a refresher, a row is considered invalid if any of its fields have a failing validation or an "error"-level message that you have placed via a data hook.

The invalidDataBehavior replaces the allowInvalidSubmit setting, and gives you three options:

  • REMOVE_INVALID_ROWS, (the default) warns the user that there are invalid rows, and if they proceed, drops the rows with invalid data from the results.
  • INCLUDE_INVALID_ROWS also warns the user, and if they proceed, will include the rows with invalid data in the results. You can check the rowsWithErrors field on the results metadata to determine which rows had issues.
  • BLOCK_SUBMIT is the new behavior that this setting enables. With this enabled, users will not be able to complete the import until they have resolved all of the errors in the import.

Filename now available in onResults callback​

In addition to the upload step hook, you can now access the filename of the user-uploaded file in the onResults callback. You will find it in the metadata object under the filename key.

Empty columns automatically dropped​

If files are imported that have columns that are completely empty, Dromo will now ignore the columns, keeping the column matching screen free of clutter.