@42.decaen I’ve been unable to replicate this issue and get the expected error when the JSON is malformed. I have pushed an update to support Bubble’s V4 plugin version. Can you upgrade to the newest version and see if you are still experiencing the same issue?
Also make sure that you are adding a condition to the action “New file from Base64” to keep that action from running if an error is thrown from the Create CSV from JSON action. The error you saw in the logs is actually coming from the New file action, not from the Create CSV from JSON action.
Step 1 = create CSV from JSON (SSA)
Step 2 = CSV Creator - New File from Base64
Step 3 = send email with an email body that varies depending on whether Step 1 resulted in an error. But when Step 1 resulted in an error, Step 2 was actually “terminating” the workflow: is that right @eli ?
And therefore Step 3 never triggered. And I thought the entire workflow was silently failing.
Therefore, as per your suggestion, I need to check whether step 1 returns an error or not (and send any success/failure emails before step 2.
That is correct. You could still keep the email in step 3 though as long as you have a condition on step 2 to only run when no error is returned from step 1. Glad you got this working properly!
Thank you for the reply. Apologies for the late response as I am not often on the forum.
Yes, I am loading in excel. Yes, I am familiar with the sorting functions in excel, but had wondered if there was a way to have it sorted before the file opens in excel?
I ask because it does actually cut down some steps in the process flow if it can be done from your plugin.
Many thanks for the beautiful plugin btw - it’s such a wonderful tool.
Hey @eli ! What are the limitations of the downloading file? When I create it for 700 rows, it works fine, on the moment I do this for 1k rows, it falls with the next error
@dariacherniakk Generally if the action works properly for one set of data but not another, there’s an issue with the data in the second set of data. In this case, I imagine it’s in the additional 300 records.
This can be caused by something as simple as a double quote being in the text that is being exported.
The way to fix this is to make sure to use the :formatted as JSON-safe operator on all your values.
So your JSON object will look like this
{
"column1": bubble_value1:formatted as JSON-safe,
"column2": bubble_value2:formatted as JSON-safe
}
Note that in the correct version that uses the :formatted as JSON-safe you shouldn’t put double quotes around the value as Bubble does that automatically when formatting as JSON-safe.
The dynamic CSV file only works for data field that are single item fields. If you want to export lists (ie multiple items in a field) you need to use CSV from Json.
hi @eli - How big would the lift be to implement partial force mapping?
Would be really cool, as I have multiple use cases where I really want the user to fill in certain fields, but have some optional fields as well.
@eli - it has been mentioned several times in the past about adding an option to export your CSV file in UTF-8 format…to account for special European Characters…Has this been added? If not is there a work around for it? We are loving your plugin but have a lot of European Characters and it comes out garbled in the CSV file…
I’m encountering an issue with CSV imports that I hope someone might be able to shed some light on. Recently, when I try to import CSV files into my Bubble application, the system is only importing the first 10 rows, despite the fact that the CSV files contain 671 lines. This limitation occurs both when using the CSV Uploader plugin (1T - CSV Uploader) and when importing directly through the Bubble database interface. This is a new issue for me; I’ve successfully imported larger datasets in the past without this problem.
Apologies for the late response as I am not often on the forum.
