When a column is dragged to the left side of the data table, it becomes a 'collection attribute' rather than an attribute of the raw data. This can be nested in multiple layers, with collections of collections of collections, etc.
When a quantity is unchecked in the PDL/PSD/CODAP wrappers, it currently does not get removed from the data table if the quantity is a collection attribute. This can lead to strange behavior if the box is checked again.
Here is an example of a disjointed state that can come from this:
To reproduce the above state:
In the CODAP data table, drag the Launcher column to the left to make it a collection attribute.
Collect some data
Uncheck the box for 'Launcher' in the sim side-menu.
Re-check the box for launcher.
Collections can also be nested, so we should make sure to solve this recursively.
When a column is dragged to the left side of the data table, it becomes a 'collection attribute' rather than an attribute of the raw data. This can be nested in multiple layers, with collections of collections of collections, etc.
When a quantity is unchecked in the PDL/PSD/CODAP wrappers, it currently does not get removed from the data table if the quantity is a collection attribute. This can lead to strange behavior if the box is checked again.
Here is an example of a disjointed state that can come from this:
To reproduce the above state:
Collections can also be nested, so we should make sure to solve this recursively.