Hi everyone another question! I have an entity that is related to others, so for a simple example say Company with many Contacts. Each Contact relates to one Company. If I do workflow to export Contacts to CSV, it basically adds a column for Company which shows the bubble unique ID. Is there any way to have the CSV file show details from the related record, such as the actual Company name, address, and other fields?
@lmoreau Did you get this worked out ? I also have a similar requirement in which I need to generate a .csv file with a related field from the other table.
Anybody else as well, if have a solution around this, please help.
Hey no I never managed to get it to work so had a custom integration with a SQL server made so I can do proper reporting off the SQL database instead. There’s some plugins that export repeating groups to CSV but still a big pain as you can’t do quick on the fly reports. Not sure why Bubble doesn’t have this capability built in.
One work around that I’ve used with “some” success is to build one page that contains the complex repeating group. Then with that page, print it to PDF. Then use the full Adobe Acrobat version to convert that PDF into excel. It works - kind of - and seemingly varies based on time of day, but it has gotten me deep into the export process quickly on a number of occasions.
This is a major pain point and constant issue that makes the platform unusable from a reporting perspective. Many of customers want to import our data into their systems for integration purposes. We have it. We simply can’t give it them because it would bury us in manual labor.
Another semi-related topic…when creating complex repeating groups that reference multiple tables, make use of the group capability to retrieve 1 Thing and then reference the fields within that Thing. It saves you making a row of data that queries the same Thing multiple times. Maybe everyone knows this, but I still find myself forgetting to do it. It vastly affects the performance of the repeating group.
One of the few limitations for Bubble. I created a workaround, but the UX is not great.
You can create a data type called “Excel Export”. All the fields are text, number, etc… none of them are relational to any other data type. Add one important field, “Report ID”. (see more on this below)
When a user clicks export, you run a Backend Workflow that creates entries to the “Excel Export” table. You are inputting the data as text or number so all values are exported using Bubble’s native exporter. You use calculate random string to add a unique report ID so that you can display it to the user.
The UX is terrible b/c the user needs to click another button to export this report you created. You could also email the report though similar to what Bubble does when you export from the db.
This has worked well so far, the CSV exporters were taking too long to run and bogging down client side.
Hope this helps
1 Like
Anyone find a true fix here?
Would be huge if bubble could solve this. I want to export a list uf users with one field as a list of friends. I can only get freind’s unique IDs and not the friend’s names. Poor UX.
@eve can we request this feature?
The fix for this would most likely be to pull all the relevant records into a repeating group, and then use the download as CSV but this time, use the repeating group records as the data source.