Skip to main content

Release notes (March 17)

Congrats on making it through the ides of March intact! Here's what's new in Dromo:

Additional settings when using the Schema Builder

Previously, if you were deploying an importer with a saved schema identifier (as opposed to the full JavaScript SDK), you were limited to the parameters available in the Schema Builder interface. Now you may change the developmentMode and headerRowOverride behavior dynamically, outside of the Schema Builder. More details are available in the docs.

Broader file type support

Dromo now offers support for all the legacy Excel formats (Excel 2007+, Excel 97-2004, Excel 2.0-5.0), spreadsheets from Lotus 1-2-3, Quattro Pro, Works, OpenDocument, Uniform Office Format, and Numbers, as well as DIF files, HTML tables, and RTF tables.

Require mapping for any field

Historically, the user only had to map required fields, in which cas any record missing a value would raise an error. Requiring mapping was tightly coupled with requiring values. But in some instances, you might want to require that a column appear in the final dataset without necessarily requiring a value for every record.

To support this, we have added a requireMapping boolean to the field object. When set to true, the user will not be able to progress to the data review screen unless this field has been matched to a column in the input file. More info is in the docs.

Version 2 is on the horizon

The entire team is heads down building the next generation of the Dromo importer. In addition to a cleaner overall design, it will feature a more intuitive column matching process, offline editing capabilities, and more powerful artificial intelligence. Stay tuned!