We should consider supporting cohort columns with more than 25 unique values (the current limit is primarily based on UX constraints), particularly in cases where values can be meaningfully grouped. For example, a dynamic widget with two linked selectors—Group → Values—could be used, where the options in the second selector are filtered based on the selection in the first. This approach would ensure that the number of options presented at any one time remains manageable (typically ≤25), even for large cohorts.
More generally, it might be valuable to introduce a tool that streamlines or automates the creation of configuration files. This could include intelligent handling of large cohort definitions, making it easier to manage complex datasets with many categorical values.
We should consider supporting cohort columns with more than 25 unique values (the current limit is primarily based on UX constraints), particularly in cases where values can be meaningfully grouped. For example, a dynamic widget with two linked selectors—Group → Values—could be used, where the options in the second selector are filtered based on the selection in the first. This approach would ensure that the number of options presented at any one time remains manageable (typically ≤25), even for large cohorts.
More generally, it might be valuable to introduce a tool that streamlines or automates the creation of configuration files. This could include intelligent handling of large cohort definitions, making it easier to manage complex datasets with many categorical values.