We've been working hard on new product features to help your teams seamlessly handle customer data, and we’re very excited to share them with you!
This month we’ve launched updates that:
Read details about each feature below.
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:
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 templates just got even more powerful.
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.
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.
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}}
We've been working hard on new product features to help your teams seamlessly handle customer data, and we’re very excited to share them with you!
This month we’ve launched updates that:
Read details about each feature below.
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:
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 templates just got even more powerful.
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.
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.
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}}
