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
We had this initially but removed it because it was doing things like turning medical codes and zip codes into measures, which is not desired. If we auto detect something, we do not want users to need to switch it back to the "default" option of dimension, when they may not yet understand what are measures and what are dimensions. It is slightly easier to understand what is happening if the values default to dimensions when they should be measures vs defaulting to measure when they should be dimensions. A measure can still be useful as a dimension, but a dimension is rarely useful as a measure.
It would certainly be nice to add this back in, but we would want to do it in a way where defaulting to dimension is the safe choice and auto detecting a numeric value that is actually a measure is the advanced logic.
Coul you autodetect for the measures upon the values? e.g. it's a measure if first 10 values are integers
Would be great
The text was updated successfully, but these errors were encountered: