-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multi-select in CSV import #5793
Comments
Just curious whether this is on the roadmap. As it stands the app cannot import its own exported CSV files due to this issue. It's also blocking me from moving my current CRM data into Twenty, as I have quite a few mulit select fields in there. This is a shame, as I'd love to start using the app. 🙂 |
/oss.gg 1200 |
Thanks for opening an issue! It's live on oss.gg! |
@thinkbig1979 sorry about that, I agree we should fix it. So much to do 😅 |
/assign |
Assigned to @DeepaPrasanna! Please open a draft PR linking this issue within 48h |
No worries! Really happy to see this being picked up. |
/assign |
Assigned to @Hitarthsheth07! Please open a draft PR linking this issue within 48h |
/assign |
This issue is already assigned to another person. Please find more issues here. |
@DeepaPrasanna, Just a little reminder: Please open a draft PR linking this issue within 12 hours. If we can't detect a PR in 12h, you will be unassigned automatically. |
@Hitarthsheth07, Just a little reminder: Please open a draft PR linking this issue within 12 hours. If we can't detect a PR in 12h, you will be unassigned automatically. |
Fixes issue #5793 (and duplicate #8822) - Fix importing multi-select and array fields. - Fix exporting and importing RAW_JSON fields. --------- Co-authored-by: ad-elias <[email protected]>
Followup of #5471, we should also support multi-select fields with comma separated values (or even a dropdown select to indicate what separator has been used). The default separator should be the same we use for exports so that people can export/re-import and it stays idempotent.
The text was updated successfully, but these errors were encountered: