Feature Requests

We've had a few users accidentally close the import workflow and close their progress. We have turned off the Close button, but it would be great if there were also a confirmation if the user clicks the X button.

There's no GET endpoint. You can create, fully replace, or partially update - but you can't read a sheet's current config back. Combined with PATCH's semantics, where only provided fields are updated and omitted fields stay unchanged, that's field-level granularity, not array-element-level. So sending sheet_columns with two new columns very likely replaces the whole column array rather than appending to it. With no GET to read the existing state first and no way to verify afterward, a careless patch could silently wipe twenty columns. So it is essential to have a GET Sheet API.

My use case is I have a column in which several other columns which fetch data from different backend sources rely on for filtering ( think multiple Dynamic Lists reaching out to different endpoints ). I would like it to be possible to have multiple dependent dynamic lists to a dynamic list column and have their data fetching be independent of the parent Dynamic List. If there is another way to filter a dynamic list column the data based on the value in another column that would work as well. I could just keep them all as separate Dynamic Lists. At the moment I don't think that is possible.

When an Excel file with multiple worksheets is uploaded, there's an interstitial that says "Multiple Worksheets detected in your file. Select one for upload." and the user selects one, and it's the one that's imported. The original_filename of the file is included in the payload, but the name of the selected worksheet is not included. If I upload a file with three worksheets, at the end I'll know that they all came from file1.xslx, but what I really need to know is that I have three distinct imports from three worksheets from within that file (and their names): (for example, file1.xslx - friends, file1.xslx - enemies, file1.xslx - neutral).

When the user uploads an Excel file with multiple worksheets, and the Allow Worksheet Selection option is enabled, they're given the option to select which worksheet to upload. They can then do another upload with the other worksheet's data. But then we have two uploads of the same file name, and we have lost the context of what differentiated one worksheet from the other. Adding selected_worksheet_name to the import_complete webhook payload would be very useful. It would be even better if, on the page where the uploader makes their choice, they had the option to give their data segment a custom name and use the Excel worksheet name as the default selected_worksheet_name. The "Show import description option" is not really a substitute, as it appears before the Worksheet Selection screen.

When the user uploads an Excel file with multiple worksheets, and the Allow Worksheet Selection option is enabled, they're given the option to select which worksheet to upload. They can then do another upload with the other worksheet's data. But then we have two uploads of the same file name, and we have lost the context of what differentiated one worksheet from the other. Adding selected_worksheet_name to the import_complete webhook payload would be very useful. It would be even better if, on the page where the uploader makes their choice, they had the option to give their data segment a custom name and use the Excel worksheet name as the default selected_worksheet_name. The "Show import description option" is not really a substitute, as it appears before the Worksheet Selection screen.

Currently, the delimiter on e.g. the multiselect_list is a single string. We face the case where some users have comma-separated CSVs with semicolon as delimiter for multi-select lists, others have semicolon-separated CSVs but with comma separated delimiters 🤷 Ideally I would hand over a list of delimiters, and CSV-Box reduces the potential delimiters for non-apostroph (like '...,list_item_1, list_item_2,...'contents to use only the delimiters not being used for the CSV-file columns itself. For apostrophed contents (like '...,"list_item_1, list_item_2",...')

We use same sheet for different actions/purposes. When customers open the CSVbox modal, we want the ability to override the title as per the action customer is taking. It would be nice to allow title to be passed from options here - https://help.csvbox.io/getting-started/2.-install-code#options

For Boolean columns, it would be nice to have the option to render them as a checkbox or switch instead of text. We have a usecase where a boolean column behaves as an override for a validation rule (i.e. if the boolean is TRUE, ignore the validation rule). For end user UX, it would be a bit nicer if they could just hit a switch instead of typing TRUE. If added, i suggest this should be an optional/opt-in feature per column.