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
When using Appearance's ranking on a dynamic column the min/max values used for the boundaries are using the column's estimator. That can be the expected behavior in some cases but is probably not the main one. What we rather want is take the min/max within the dynamic attribute (i.e. reviewing each value).
Expected Behavior
Min and Max values within dynamic attributes are used, instead of estimators.
Current Behavior
Ranking min/max always use the column estimator.
Possible Solution
It could be an extra configuration we display for dynamic columns. Estimator selection is anyway buried in the timeline component so it would be handy to display it there, to make it clear what is used to compute the values.
When using Appearance's ranking on a dynamic column the min/max values used for the boundaries are using the column's estimator. That can be the expected behavior in some cases but is probably not the main one. What we rather want is take the min/max within the dynamic attribute (i.e. reviewing each value).
Expected Behavior
Min and Max values within dynamic attributes are used, instead of estimators.
Current Behavior
Ranking min/max always use the column estimator.
Possible Solution
It could be an extra configuration we display for dynamic columns. Estimator selection is anyway buried in the timeline component so it would be handy to display it there, to make it clear what is used to compute the values.
Steps to Reproduce
Context
Reported on FB group by Andy B.
Your Environment
The text was updated successfully, but these errors were encountered: