Export Table Data

[Al-Blu]

Hi,
I need to export a table. I would like to have the possibility to do it manually as Admin and also allow the User to export using a button-action. The BD-Table is a mySql external DB.

If I do it manually I get an error:

If I do it using an action I get the following error, but I actually want to export the full table.

Can you advise me on how best to achieve this? Is there some tutorials or docs I can look at?
Thanks

[melohagan]

Hi @Al-Blu

For the first screenshot, do you see any error messages output into the Console or Network tab?

[Al-Blu]

This is everything:

[Al-Blu]

[melohagan]

That does look very similar to the issue I referenced. I'll link this discussion as well.

[Al-Blu]

Ok then I will wait and see what happens with the Bug.

[archeopternix]

Content Security Policy is a browser feature and it has nothing to do with a 404 error which is triggered by the webserver.

A 404 error is an [HTTP status code] that means that the page you were trying to reach on a website couldn't be found on their [server]

[PaulMcF1987]

@melohagan @Al-Blu

Is there any update on this? I cannot export data either

If I try with no rows selected, I get an error asking me to select rows, when I do select rows, I get:

I also get an error when I check console:

Could this be related to what I have asked here and be caused due to having formula columns?

[jmlaurenti]

Same problem on my side, with Self-Hosted 1.0.184 / MySQL table.
It's working when exporting data from Data View, but not from Export Data action in code (error 400 like @PaulMcF1987 ).

[hreinberger]

yep, I see the exact same behavior. MySQL Data Source, super simple table layout.

[PaulMcF1987]

@melohagan
The issue on my side does not appear related to any security concern, instead it appears to be the empty columns
I can export from the control panel but am unable to export from within the app

[jmlaurenti]

Yep, exactly the same error 400 "cannot convert undefined or null to object", even when all fields are filled (MySQL DB / Budibase 1.0.218)

Not sure how to proceed to have this problem being considered, I guess CSV export is a pretty common requirement ? :-)

[melohagan]

@Al-Blu @PaulMcF1987 @jmlaurenti @hreinberger

This bug should be fixed in the next release which is within a week!
#6354

[jmlaurenti]

Thanks @melohagan ! :-)

[jmlaurenti]

Just tried, and it works :-)

[PeterAronZentai]

Apparently this is broken again.

[melohagan]

Hey @PeterAronZentai

No bug here! As the message indicates, you need to select at least one row. Looks like your table does now have the Allow row selection setting ticked.

[jowkar]

Getting this error when trying to export from a table constructed from an SQL query (which performs a join). It seems that it is not possible to add row selection check boxes to such a table (enabling "Row selection" in Table settings does nothing and no check boxes appear on the published page), presumably because row selection is not supported for query results. This becomes a problem when exporting data requires row selection, which I can't find anyway of getting around. Also tried creating a view in PostgreSQL (which the app is connected to) in an attempt to work around this by importing the view instead of constructing a table in budibase from an SQL query. However, attempting to import a view from PostgreSQL gives an error saying that the view does not have a primary key. Since adding primary keys to view are not supported in PostgreSQL, such views are essentially not supported at all in budibase. So I cannot find any way to successfully get the export data function working on a result of a table join.

[melohagan]

Hey @jowkar Table row selection does not work for custom queries.

As an alternative you could try the community Power table plugin that does support row selection for custom queries, at least at the page level.