You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of EMX2 are you using (see footer) v11.31.2
Describe the bug
Exporting all data from a database as an Excel-file doesn't work - it takes a while to load, displays a blank page and no file is downloaded. Exporting as Excel for specific tables does work for most tables, with the exception of Resources and Subpopulations.
The backend throws and exception that is not properly handled. The reason is that testCohort1 has 676 disease terms in the column 'population disease'. This exceeds 32767 character limit of an excel column. I can make sure this error is shown in the frontend, but this will not solve this problem.
We will need to handle the way we store these disease terms differently to stay within the 32767 char limit, if having this many terms for a cohort is realistic.
I encountered the same issue for BBMRI-ERIC Directory. Even for a National Node with hardly any information. After some debugging it turns out that it is in the molgenis_settings.csv. Which probably also exceeds the cell value limit.
However, when I use the Excel function in https://MYSERVER/MYSCHEMA/tables/#/, I would expect to only get the data and not molgenis_settings, molgenis_members and molgenis. (Even when I'm a user with role = Editor who does not have permissions to see the settings via the application...).
What version of EMX2 are you using (see footer)
v11.31.2
Describe the bug
Exporting all data from a database as an Excel-file doesn't work - it takes a while to load, displays a blank page and no file is downloaded. Exporting as Excel for specific tables does work for most tables, with the exception of Resources and Subpopulations.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A file should be downloaded and the up/download page should remain displayed.
Version info
MacOS Sequoia, Firefox 133.0
The text was updated successfully, but these errors were encountered: