Changelog

We understand every company's file ingestion process is unique. That’s why a focus for OneSchema has always been enabling companies to optimize OneSchema’s import workflow for their specific use case. To further expand on the customizability of OneSchema, we’re introducing Import via API.

‍For workflows that ideally involve a blend of managing some portions of the import process internally while still using OneSchema to handle the rest, initializing the importer via our API provides a great solution.

A new modal has been added to the end of the Review & Finalize pane that allows you to accept only rows without errors. For use cases where you’d like to get as much data in as possible but ingesting all of the user’s data isn’t critical, this is a great option to increase your import conversion rates.

The new modal addition:

1. Allows your user to submit clean rows without having to fix every single error in their data
2. Gives end users the opportunity to export the remaining errors so they may fix their data in Excel and re-upload it into your system.

Note: This modal will only appear if there are remaining error rows in your end user’s upload when they attempt to import.

OneSchema will still send the final JSON export with clean rows as “records” and error rows as “error_records.” This way, even if your user never returned to clean the rows with the remaining errors, you still have a record of the data not imported.

The importer will now skip the mapping step if all template columns are matched (exact match) in the list (and header row selection was also skipped).

You can now customize the first pane of your CSV import experience to include a summary of the data you’d like your customer to import. You can include your required and optional fields and descriptions of the data the customer should upload.

We added the following optional customizations to empower you to create the ideal experience for your end users on the first pane:

• The header and subheader copy within the Uploader component can now be fully customized
• Show the required columns and their descriptions in a new InfoSideBar component
• Show the required and optional columns along with their descriptions in a new InfoSideBar component

You can learn more about how to enable these customizations in our docs.

OneSchema now supports the ability to fully translate the UI into the language of your choosing. Internationalization is currently an enterprise-tier feature. Please reach out to us to discuss your team's i18n needs and desired language support. Supported languages include: English, Spanish, Portuguese, French, German, Swedish, Chinese (Simplified), Czech, Danish, Dutch, Finnish, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Arabic,

Learn more about the configuration option in our docs.

We’re very excited to announce our most requested feature: guided error fixing. In our beta tests, offering helpful suggestions for resolving errors has driven substantial uplift in import conversion rates. These upgrades include:

• Error Fix Suggestions: OneSchema will offer suggestions to your customer to fix errors, contextualized to the type of error your customer is encountering.
• Navigate to column with errors: When clicked in the issues summary, OneSchema will now pull the column with issues directly into view.

Bulk deleting rows:‍

• Delete all rows with errors: OneSchema now contextually surfaces the option to delete all rows with errors, allowing customers to progress in their import workflow. Alternatively they can “Export to Excel” to get a summary of their errors.‍
• Delete selected rows: “Delete selected row(s)” button when selecting rows will be shown to users‍

We are also launching usability improvements based on customer feedback:

• Issues Sidebar: Issues summary sidebar will no longer obstruct the last few columns in the sheet. Instead, it will appear inside of the spreadsheet view.
• Filter to find errors: We’ve added a “show error” button in the issues summary that when clicked, brings the error front-and-center. It’s never been easier to find errors in your file.

An activity feed of all successful, failed, and unsubmitted imports are now available to view via the Developer Dashboard. This will let your team review information about the files that are being imported by each of your users. To help your customer success teams easily provide troubleshooting support on failed imports, we’ve also added the option to download the original files uploaded by your users.

We’ve updated the version of our Javascript and React SDKs to v0.2. Updating the version will require some small changes to initialization and passing in configuration options.

‍See the new documentation here:‍

Javascript: https://docs.oneschema.co/docs/javascript

‍React: https://docs.oneschema.co/docs/react

We’ve improved our picklist data type error resolution to support multi-value picklists. Your users can now resolve any delimited picklist columns with ease in the same way they would for single value picklist columns.

To streamline the import process, users who upload a file with a header row will now skip the Header Row Selection pane and be taken directly to the Map Column pane. Header rows are automatically identified based on a number of criteria. To learn more about how we identify the header row, visit our changelog here.

To enhance the template creation process as well as the implementation experience, we’ve released a sandbox of the Importer. This will allow you to see the Importer in action without any additional effort and quickly test new or existing templates with real files.

Your users will now be prompted to map their picklist values to the set of values that you specify within a template. Picklist mapping will help eliminate any unrecognized, undesired, or incorrect values from being in the imported data.

We’ve improved our column matching algorithm so your users’ uploaded columns will be automatically mapped to template columns during the Map Column pane more often. In addition to mapping columns that have exact column names, OneSchema will also remember historical mappings that your users may have successfully imported in the past. You can learn more about how our mapping intelligence works in our changelog.

You can now enable template columns to automatically fill a value of your choice into the mapped column’s empty cells.

‍Note: This is only available to customers whose Importers are using our new Rust architecture. Please reach out to your account manager if this feature isn’t available in your Create a Template column modal.

You’re now able to customize the appearance of the OneSchema Importer through our developer dashboard! You may customize the primary color of the Importer to better match your brand colors and import a custom font via URL (e.g. Google Fonts or Adobe TypeKit). You will also be able to hide the OneSchema logo as long as you have committed to our annual subscription pricing.

We’re actively working on bringing you more granular customization options to better fit in with your product styles — if you have any particular requests, please let us know.

Angular SDK is now available for users who would prefer to build the OneSchema Importer using Angular.

Our spreadsheets are running on new infrastructure! Our engineering team has built a new spreadsheet data service in Rust that loads every uploaded file fully in-memory. The spreadsheet files will live on new high-memory servers that make it possible to validate and transform files of up to 4 GB in under 1 second.

Files of up to 1,000,000 rows can be:

• Uploaded in under a minute.
• Validated in under a second.
• Auto-fixed and transformed in under a second.

You’re now able to customize the appearance of the OneSchema Importer through our developer dashboard! You may customize the primary color of the Importer to better match your brand colors and import a custom font via URL (e.g. Google Fonts or Adobe TypeKit). You will also be able to hide the OneSchema logo as long as you have committed to our annual subscription pricing.

We’re actively working on bringing you more granular customization options to better fit in with your product styles — if you have any particular requests, please let us know.

Your users will be presented the option to select which worksheet within an Excel workbook they want to upload.

Note: This pane will only appear for users who upload an Excel Workbook with multiple worksheets. CSV uploads and single sheet imports will not trigger this modal.

You can now grant and revoke team member access to OneSchema directly from the developer dashboard.

From our new Template Settings, you can now allow your users to upload and import custom columns from the Importer.

Your users can map any of their uploaded columns as a custom column. Custom columns come with default string validations but can be customized with additional validations from the Template Settings page.

The UI for the Map Column pane has been updated. We’ve added more visual separation to delineate your user’s uploaded columns from the template columns. We’ve also improved the delete UX to make it clearer that columns are deleteable and will not be imported as a result.

These changes do not require any additional configuration from you.

Write custom descriptions for any column you feel your users could use additional context or instructions. These descriptions can help guide them through the mapping process and during the final validation step. Descriptions will appear in context to each column, both in the Map Column pane and the Review pane.

External validation hooks now also support column hooks in Rust. Below are the differences between the existing external row hooks and the new external column hooks:

‍Configuration differences: If the hook type is `column` the batch size can’t be configured since we always send all rows for column hooks. As you can see in the screenshot we also show a warning banner since a slow column hook could result in a bad user experience. The reason for this lies in the behavioral differences.

‍Behavioral differences: When a single value is updated by the user we send only send the edited row for row hooks.  For column hooks, we send the whole affected column which can be slower depending on the logic implemented by our admins.

‍Gating: The gate `ColumnHooks` has to be active in order to create and use column hooks. If the batch size doesn’t show up the `InMemoryListStorage` gate is not active.

The launch of our ready-made CSV importer for developers which automatically corrects customer data. (Also: edge case handling, simple UI, bulk editing).

Create custom templates for each of your users. Generate templates via code and create an import experience tailored to your customer’s unique needs.

While OneSchema makes the overall process of data migration much faster and far less painful, security and compliance are always top of mind as our customers trust us with their customer's sensitive business data and PII.

We are extremely excited to share the news today that OneSchema has now achieved SOC2 Type II compliance.

Users can now download annotated Excel files with their errors highlighted, allowing them to collaborate with other users on error correction.

At OneSchema, we’ve created the largest proprietary library of data validations available, designed for all industries. With our pre-built validators, even non-technical team members can configure your template(s) without asking an engineer for a single line of code – all while saving your team the enormous cost of building and continuously maintaining validations every time your database schema changes.

With OneSchema, setting up a validation is as easy as giving the column a name, selecting a validation from the dropdown, and optionally ticking a few boxes. We’re continuously testing our validators against messy CSV data of all types across our customer base, updating them to handle the never-ending list of new edge cases, and adding new ones so your team can focus on building your core product.