BUG: Workspace data corruption
Some of the workspace data is corrupted when exporting to tsv and importing back.
If I have lists (of strings) in my workspace data, when I round-trip the workspace variable becomes a single string consisting of the elements of the list: so the array: ["one","two","three"] (consisting of three strings) becomes the single string "[\"one\",\"two\",\"three\"]"
Additionally, if one has custom "column views", they are exported from one workspace inside the workspace data but are not properly imported (they do not become custom views, but they do become visible and confusing workspace variables.)
Thanks for writing in! I'm going to investigate this, and I'll let you know what the next steps are going to be.
I wanted to let you know that I was able to replicate the string issue you were having and I've passed the issue along to our engineering teams to take a look. I'll let you know once we have any updates.
As for the issue you're having with "column views," can you share the workspace where you are seeing this issue with Terra-Support@firecloud.org by clicking the Share button in your workspace? The Share option is in the three-dots menu at the top-right.
Please provide us with a link to your workspace. We’ll be happy to take a closer look as soon as we can!
I already "fixed" the issue (i.e. deleted the offending row in the workspace data table) to recreate do the following:
0. Have a workspace with some entity data, and another workspace to use later.
1. Create a saved custom column view for that entity from the first workspace
2. Export the workspace data table as TSV
3. Import the tsv into the second workspace
4. There's now a "columnSettings" variable in the second workspace data, which doesn't actually create a custom view in the workspace.
I'm glad you were able to resolve the issue you were having with Column views. Let me look at the steps you've provided and if I get the same issue, I'll let our engineering teams know.
I wanted to give you an update on this: While I wasn't able to recreate the "column views" issue, but I have filled a bug report with our Engineering teams for the string issue as I have stated before. I will contact you once that bug has been resolved.
Please sign in to leave a comment.