Skip to content
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

🐛 Bug: unable to download table data ((t || []).map is not a function) #5552

Closed
1 task done
ilyak0 opened this issue Apr 27, 2023 · 16 comments
Closed
1 task done

Comments

@ilyak0
Copy link

ilyak0 commented Apr 27, 2023

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

Any download results in the same error
image

image

Desired Behavior

Need to get the file downloaded

Project Details

Node: v16.19.1
Arch: x64
Platform: linux
Docker: true
RootDB: mysql2
PackageVersion: 0.106.1

Attachments

No response

@wingkwong
Copy link
Member

I'm not able to reproduce the issue. Can you show the schema?

@ilyak0
Copy link
Author

ilyak0 commented May 4, 2023

Just opening the first table and trying to download the files... Nothing special
Other tables in the base are easily downloaded, only the first one causes this issue

image

@wingkwong
Copy link
Member

Can you share the list of column types you have in that table? Also are you downloading as CSV or XLSX or both failed?

@ilyak0
Copy link
Author

ilyak0 commented May 4, 2023

Both fail

image

image

image

image

@wingkwong
Copy link
Member

do other tables (except the first one) contain attachment fields?

@ilyak0
Copy link
Author

ilyak0 commented May 5, 2023 via email

@ilyak0
Copy link
Author

ilyak0 commented May 18, 2023

@wingkwong any news on that please?

@wingkwong
Copy link
Member

@ilyak0 I still couldn't reproduce the issue.

@ilyak0
Copy link
Author

ilyak0 commented May 18, 2023 via email

@ilyak0
Copy link
Author

ilyak0 commented Jun 1, 2023

Here's the docker log for example, however may be not too informative.. https://pastebin.com/wQ9vU18k

@wingkwong

@abovesky
Copy link

abovesky commented Jul 4, 2023

I have also encountered this problem, and no matter what fields are included in the first table, the download will fail.

@ilyak0
Copy link
Author

ilyak0 commented Jul 20, 2023

@shashankvish thanks for looking into it. What kind of info may help you pls?

@ilyak0
Copy link
Author

ilyak0 commented Jul 25, 2023

@wingkwong is there any further info that we can help you look into this issue?
Considering that we're unable also to copy the cells in the same base as per #5333
now we are literally unable to export the data from the table...

I believe @abovesky would also be happy to provide you with some further details if needed

@wingkwong
Copy link
Member

@ilyak0 Sorry for the wait. So far it's hard to debug given that I don't have a reproducible environment. I guess the error may be thrown from papaparse and your attachment value format got messed up. Can you try the following?

  1. Disable all attachment fields, are you able to export the table?
  2. Enable all attachment fields back (i.e. undo above step), Create a formula referencing on one of the attachments, check if there is a difference between new records and old records. Copy the value and send to me via Discord. I wanna verify the attachment value structure.

@dstala
Copy link
Member

dstala commented Oct 28, 2023

@ilyak0 please try our latest release v0.202.5; if issue still persists, please reopen this thread.

@dstala dstala closed this as completed Oct 28, 2023
@rossmills99
Copy link

I can confirm I see the same issue on v0.202.5,

The table in question has a lookup field, which itself is an attachment. If I hide that column (deselect it in the Fields dropdown), then I am able to download the data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants
@o1lab @rossmills99 @abovesky @wingkwong @dstala @ilyak0 and others