Skip to main content

Release notes (July 1)

React to row deletionsโ€‹

On Dromo's review screen, your users have the opportunity to delete any rows that shouldn't be there by right clicking on a row and selecting "Remove row".

If you need to react to this situation programmatically, this is now possible with row delete hooks. As you might guess, they will fire any time a row is removed, with relevant information about the removed row.

Give your user the low-down during slow-running hooksโ€‹

If you have hooks that do long-running tasks like accessing slow external APIs, sometimes you have no choice but to keep your user waiting while they run.

Now, you can provide your users with some context while your hooks are running at the beginning of the Review step. Just set the reviewStep.processingText setting to the message you want to show the user.

The processingText setting in action

More metadata about fields and headersโ€‹

Hooks unlock the full power of Dromo, allowing you to deeply integrate the upload process into your app. We are always looking for ways to make them more powerful, and one common request was to have more context about the original file and how it was mapped.

The REVIEW_STEP and REVIEW_STEP_POST_HOOKS hooks as well as the onResults callback now provide you with comprehensive metadata about all of the fields that will be present in the results. As always, full information can be found in the docs.

Is there something you would like to see in the hooks? Let us know!

Opt out of fuzzy matchingโ€‹

When your user imports a file, we do our best to save them time by matching the file headers to the fields in your schema. As with all fuzzy matching, it's possible for these suggestions to sometimes be wrong.

If you have some critical column matching that is evading our matching algorithms, you can now opt out of the fuzzy matching functionality by setting matchingStep.fuzzyMatchHeaders to false.

Bugs squashed ๐Ÿ›โ€‹

  • The Dromo uploader will no longer show a warning to the user when they go back from the Review step if they have not changed any data
  • Fixed buggy behavior when attempting to automap a field that no longer exists in your schema
  • Improved behavior when making rapid edits in combination with slow-running row hooks