Changelog

We've added a customization that allows customers to add a maximum row limit that can be imported, and they can also add an optional custom header and description message for this error. When this customization is active and there are more rows than the specified limit, we will display an error in the importer and block the user from continuing with the import.

We've added a customization option that allows you to add education widgets to your importer! This enables you specify different widgets for each of the 4 Importer panes, have it default open or closed, and supports markdown.

We're excited to roll out environment scopes for API keys, which enables those keys to only access embeds in the prescribed environment. This helps customers uplevel the security of their organization by ensuring that their developers' local and staging environments should not have access to customer PII.

The cell popover for errors and warnings with suggestions now has a new button, "Accept for X cells". Clicking this button will accept all suggestions for cells in the column that have exactly 1 suggestion, making it even easier for your users to clean their files. The button will appear for users if there are at least 2 cells in the column which have exactly 1 suggestion.

With Picklist Descriptions, you can now use template overrides to set descriptions for each individual picklist option. These will be displayed in each dropdown of the OneSchema importer:

- Picklist mapping

- Picklist cell editing

- Picklist error popovers to replace all

These 3 improvements to picklists help customers whose use cases require long picklist values to be inputted:

1. Picklist pills will now truncate properly with a tooltip on hover to show the full value
2. The base width of the dropdown has just naturally been increased 20% across the board
3. The width of the dropdown will now actually increase if the column width increases

This new customization option under the "User Education" tab enables an informational sidebar on the mapping pane for your users. This will display a green check next to columns that have been mapped, and update dynamically as users select their mappings.

Users now have the ability to generate a sample test file for a template, eliminating the need for a file on hand to experience the importer. The button to generate a sample file lives can be found in the sandbox preview below the importer. The generated data will mostly conform with the template column options, but the data may not be 100% valid according to the template.

We've launched an update to our number autofixer, which can now handle negative numbers in account format. You can utilize this to automatically correct entries formatted as (100), and automatically change them to -100.

Our new Alternative Picklist Names feature enables you to specify one or more "alternative_names" for each picklist value via template overrides. If any of the alternative names appear in the uploaded file, they will automatically be mapped to the picklist value.

The number data type now has a new selection for the format, either be "US" (the default), or "EU". The EU number data type uses "," as the decimal separator and "." as the thousand separator.

The external API keys page has been updated so every user can see all external API keys in their organization. With these changes, a user can create multiple keys, set a label, and see when an API key was last used. In addition, deleting a user also now does not delete any API key(s) created by that user.

OneSchema now supports Fullview as a screen recording provider, allowing customers to analyzing recordings of their customers using OneSchema and optimize the experience.

Customers can now use the "Required Column Groups" feature to set that at least one column in a group must be mapped.

Our new Boolean data type feature allows users to define true and false values more easily.

You can now set specific colors for each picklist option! A list of 10 default options are provided, but exact HEX values can be used as desired.

Customers can now set environment variables in webhook keys. This helps customers who want to keep their secret keys isolated across different environments.

OneSchema Pipelines lets non-technical team members (account managers, operations) setup recurring CSV integrations with your customers’ complex data feeds without engineers getting involved. Map, transform, and ingest CSV files via SFTP, API, or email without needing to write a single line of code.

Customers can now select which environments to push when creating dynamic templates.

Customizations and Templates determine the behavior of OneSchema Importers. Using overrides can allow specific behavior for individual importing sessions. Customers now have the ability to define validation hooks in template overrides.

We've launched a feature to split Historical Matching into User-specific and Org-level matching. Previously, this only worked on the org-level. This helps customers whose users are differentiated enough that they do not want to have cross-user mappings be saved.

Customers can now use environment variables in Importer Webhooks

Environments allow you to safely push and validate changes to templates in stages to align with the environments in your deploy process.

OneSchema automatically sets up environments for Production, Staging, and Development. See our guide on custom environments to set up custom environments.

We’ve made improvements to our Template Overrides functionality by adding the ability to add and remove columns from the overrides.

We’ve made improvements to our custom code transformations and validations, also known as OneSchema Code Hooks. These Code Hook upgrades aim to greatly enhance both how your team builds custom functions that support your company’s unique business logic, as well as how your end-users experience the OneSchema Importer.

A new post-upload hook now exists for transposing (swapping the rows and columns) of a file.

To better support end users with bulk error resolution, we’ve improved our copy and paste functionality on the Review & Finalize pane to enable multiple cell copying and pasting.

We’ve added UI for end users to immediately filter for all rows, only rows with errors, or only clean rows.

String Replacements allow you to change the headers and buttons of every step of the importer. This can be helpful if there’s an existing string inside of the importer flow that you feel could be edited to better fit your existing brand (or use case).

For some customers, an end user deleting a row of data prior to import can break their entire flow. We’ve added a customization option that allows you granular control over how and if the end user should be able to delete rows from the Review & Finalize pane.

Admins can now specify the particular date format that’s expected for template columns instead of relying on OneSchema’s date detection (which defaults to a month, day, year interpretation). This impacts scenarios where a file’s uploaded date column contains a majority of ambiguous dates, and the format is not MM/DD/YY (e.g. 01/02/2022 can be either January 2nd, 2022 or February 1st, 2022).

Custom columns can now be supported inside of validation webhooks. Review our updated docs to understand the different use cases, how to set up custom columns, and example JSON POST/responses.

To provide further customization of our Upload pane, the optional message box can now be customized using Markdown. Our customers can insert URLs to additional data import resources for the end user.

JSON object is newly available as a data type validation for template columns.

Customers can now choose to return a list of suggestions from a validation webhook. End users will be prompted to select one of the suggestions as a part of the error resolution process.

OneSchema’s money data type validation and autofix feature now supports the Pound (£), the Euro (€), and the Yen (¥) currency symbols.

The error messaging for the Number data type and Money data type has been improved so end users can better understand why the value is invalid and how to fix it.

Rather than sending batched rows of data to a customer webhook, sheet metadata can now be sent via webhook. This is significantly faster and also enables you to directly use the metadata to retrieve data via external API (e.g. GET rows for paginated JSON or POST sheets for S3 URL download of CSV/excel/JSON).

Since we’ve started building OneSchema, one of the deepest pain points we’ve seen in our customer base is building and maintaining recurring spreadsheet import workflows. Expensive engineering teams have to write brittle scripts to ingest the data, and spend countless engineering months maintaining validations to make sure all customer data is being imported correctly.

In the case of a failure, it’s extremely painful for the technical team to track down the root cause of the failure, and all the while the customer is frustrated because their data isn’t up-to-date in your product. OneSchema Headless empowers engineering teams to leverage OneSchema’s mapping, validation, and error resolution capabilities to painlessly build custom integrations with a wide variety of data sources, like SFTP/S3 file drops, CSV email attachments, messy API data, and more.

Users can now see logs of their importer and validation webhooks (up to the past 14 days). This should enable users to better debug their webhooks when they run into errors, and enable your teams to monitor webhook activity.

Customers can now instruct OneSchema to send processed files directly to their own presigned URL.

Customers now have the option of having OneSchema instances hosted in Canada.

Customers now have the option of having OneSchema instances hosted in Australia.

Because our customers span a variety of industries, we often see workflows that come with unique business logic built into their specific datasets.

To make OneSchema even more flexible for these custom use cases, we’ve created OneSchema Code Hooks. Code Hooks empower your engineering team to generate tailored functions to reformat, transform, and/or validate data specific to your business's needs inside of the importer flow.

Similar to historical column mapping, historical picklist option mapping remembers mappings and pre-fills the values for subsequent uploads. This behavior is active if the “Historical match” customization in the “Map columns” section is set.

Sessions can now be resumed in case a user's browser crashes or they do not finish an import. To enable this feature, update your SDK to the latest version(0.3.3) and pass in the param saveSession as true. Then sessions using the same userJwt and template key on the same browser will be prompted on resume as seen in the screenshot below.

OneSchema templates just got even more powerful.

• With the alternative mappings feature, you can tell OneSchema which mappings you’re expecting to see so that your user won’t have to map them manually.
• Use fill default values to automatically fill in empty cells instead of leaving them blank
• Check out the flexible options on our data type validations that let you validate everything from digits after the decimal to excluding special characters.

We've also redesigned the template column creation modal to better organize all the different data validations options and to make template creation easier for you.

You can now host OneSchema inside of your AWS or Azure cloud environment. The self-hosted model provides full isolation of data in your own cloud, and is best for customers who are handling government data (GovCloud), or other extremely sensitive data with unique contractual / compliance requirements. OneSchema will deploy updates and maintenance to the platform through an IAM user.

A dashboard with granular UI customizations is now available for you to make the OneSchema Importer look and feel like your existing product UI! We’ve also updated our default icon set and illustrations to be more brand-neutral, to help OneSchema’s Importer fit better in any product, even without customizations.

A dashboard with granular UI customizations is now available for you to make the OneSchema Importer look and feel like your existing product UI! We’ve also updated our default icon set and illustrations to be more brand-neutral, to help OneSchema’s Importer fit better in any product, even without customizations.

With our Branding Suite, you can now access 20+ customization options, including:

• Primary, secondary, and background colors
• Buttons
• Success, Warning, and Error states
• Custom illustrations
• Font family and font colors

Watch this 3 minute step-by-step demo of the OneSchema Branding Suite that demonstrates how to fully customize your importer's color, font, and more.

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.

OneSchema webhooks let you send data to your ingestion endpoint but can be slow for very large files.

Now, OneSchema can put your exported file into an S3 bucket, where you can retrieve it as JSON or CSV. This makes exporting large files far more performant.

To enable this new feature, a new OneSchemaConfig has been added: skipExportData. This changes the behavior of the success event (onSuccess callback in React) when not including a webhookKey. Instead of sending all of the data from the list, we will only send the sheet_id. You can then use API v1 to download a file or use our Paginated JSON Get end point.

We recommend this config option for customers who anticipate their end users will upload large files but don’t want them to wait for the file to finish processing before proceeding back to their workflow.

You can learn more about the config in our docs.

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.