Introducing OneSchema Code Hooks
Code Hooks makes OneSchema even more flexible for use cases with unique business logic. Empower your engineering team to generate tailored functions to reformat, transform, and/or validate data.
July 31, 2024
Engineering and product teams use OneSchema to easily launch delightful spreadsheet import experiences. 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.
There are three types of Code Hooks, which each execute at a different point during the import process:
Visit our Code Hooks docs page to learn more about Code Hooks and see some example code snippets.
Post-upload Code Hooks modifies data right after it’s been uploaded. Your user’s uploaded file arrives in a nested format. Before it can be processed through OneSchema, you want to flatten it into something more usable.
Post-mapping Code Hooks transform data after the uploaded columns have been mapped to a template. A common use case we’ve seen is to split and merge columns prior to import (eg. Full name -> First name, Last name). You can also use post-mapping code hooks for deleting columns and adding empty columns (plus filling it with a particular value).
Validation Code Hooks surface errors and warnings on individual cells during the Review & Finalize pane. A common example of when this is helpful is to check for multi-column uniqueness – this will flag when values in separate columns that are paired up appear in more than one row of the dataset.
Validation Code Hooks can also be used for:
Learn more about implementing a Code Hook via our API Reference.
As always, we welcome your feedback on these changes! Please feel free to share feedback by reaching out to founders@oneschema.co. We'd also love to keep in touch on LinkedIn.
{{blog-content-cta}}
Engineering and product teams use OneSchema to easily launch delightful spreadsheet import experiences. 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.
There are three types of Code Hooks, which each execute at a different point during the import process:
Visit our Code Hooks docs page to learn more about Code Hooks and see some example code snippets.
Post-upload Code Hooks modifies data right after it’s been uploaded. Your user’s uploaded file arrives in a nested format. Before it can be processed through OneSchema, you want to flatten it into something more usable.
Post-mapping Code Hooks transform data after the uploaded columns have been mapped to a template. A common use case we’ve seen is to split and merge columns prior to import (eg. Full name -> First name, Last name). You can also use post-mapping code hooks for deleting columns and adding empty columns (plus filling it with a particular value).
Validation Code Hooks surface errors and warnings on individual cells during the Review & Finalize pane. A common example of when this is helpful is to check for multi-column uniqueness – this will flag when values in separate columns that are paired up appear in more than one row of the dataset.
Validation Code Hooks can also be used for:
Learn more about implementing a Code Hook via our API Reference.
As always, we welcome your feedback on these changes! Please feel free to share feedback by reaching out to founders@oneschema.co. We'd also love to keep in touch on LinkedIn.
{{blog-content-cta}}
