Currently, the aggregation function depends on the type of the dimension : - Text or date => Distinct count - Numeric => Sum In our use case, this default assignation is not always accurate as it ...
Hi Dray,
Let me try to clarify my idea.
1. From Data Model Design :
In the menu to set options for the tables / columns (see print screen below), having a new option "Default agregation function".
A drop down list with options : Sum / Count all / Count unique / Min / Max / Average / Median / Variance / Standard deviation, along with "Duplicate" / " Rename" / "Hide" ...
The example below (field NB_CMAD) is a numeric. Because of the type, the default option will be set to Sum. But, thanks to the menu I propose, the Data model designer will have the option to change it to something else (like "Count unique" in my example)
2. From the Widget design
The widget designer will be proposed "Count Unique" by default instead of "Sum" as they have now (see print screen below)
Of course there will still be the "More" option for the widget designer to change the agregation option if needed.
=> This way, the Data Model Designer - who knows best what is the right agregation function to apply - will have the control over the default option.
Hoping this is clearer now. Let me know.
Best regards,
Franck