While trying to export around 30000 entries from the database using json to csv action, I get an error saying “Workflow error - Plugin action inputs too large, should be less than 6MB.”
Does anybody know of another scalable method to allow users to export data, the action should be scheduled from the front end, processing and sending them the csv can be done server side.
I do not want exports from the editor, as I want users to be able to export the data.
Data sets are also going to grow larger in the future, so I need something scalable.
Yeah, this is to avoid timeouts on the front end. Have already implemented this solution. There is another limit on the backend for file size. Once it crosses 6mb (not time related)
@dev86 This is a Bubble limitation. If the JSON is more than 6mb it will error. Make sure to follow the tutorial above around timeout issues to minimize the size of the data being passed to the action but if you are doing that and it’s over 6mb you’ll have to break up the export.
Thanks Eli. Using the plugin is great – mission critical to my app.
This video is also great, but you left me hanging on passing the final JSON to the Create CSV from JSON action. If I generate the final JSON in the back end, how do I have the front end wait and then create the csv when it’s done?
Alternatively, I’d email it with the Postmark plugin, as an attachment. I don’t want to be sending my users an email with a link. Their university admin email system will filter it.
Hey guys, i implemented a report and had the problem with the 6MB limit, my solution for now was reduce the data being exported, i had a field that had only one repeated information, i removed this field and set the CSV file name to have the information of this field.
This reduced the size of my JSON to bellow 6MB and for now this is working.
After converting the JSON to CSV, i’m using Brevo Mail to send an e-mail with the report file attached to it, using the Brevo API you can attach files directly into the e-mail message.
I’m looking for a long term solution for this problem, but right now all i’ve found is that i need to use an external service to do this process and avoid dealing with this data treatment inside bubble back end work flows.
