Bug
When a dataset contains columns that are completely unpopulated or empty (100.00% missing values), the application's visualization engine fails to skip or handle them safely. Instead, it forces them into the active scatterplot matrix, rendering massive, solid brown blocks and empty layout squares.
Also, this breaks the sidebar profiler logic, causing it to default to a category count of 1 and an incorrect mode of N/A.
- note: this time the app didn't read the name of the dataset either, catalogue it as "unknown table"
The system should drop columns with 100% missing values from the matrix entirely, rather than wasting valuable screen space plotting null against null.
Dataset used
Macroeconomic GDP dataset
Screenshot
Bug
When a dataset contains columns that are completely unpopulated or empty (100.00% missing values), the application's visualization engine fails to skip or handle them safely. Instead, it forces them into the active scatterplot matrix, rendering massive, solid brown blocks and empty layout squares.
Also, this breaks the sidebar profiler logic, causing it to default to a category count of
1and an incorrect mode ofN/A.The system should drop columns with 100% missing values from the matrix entirely, rather than wasting valuable screen space plotting null against null.
Dataset used
Macroeconomic GDP dataset
Screenshot