Table View Group Aggregate is kinda confusing?
Imagine showing a table with 3 columns, each one with 30 values.
Group Aggregate is chosen to present the sum of ONE of those columns.
While the App Creator will know (well, maybe even he will forget) which of those columns was chosen to be summed in Group Aggregate, most users wonยดt know. If values are similar (letโs say, Gross Value, Liquid Value, etc) it may require a user to sum the many rows by calculator to know to which column the value is refering to.
Which is one more reason why there should exist, on Table Views, a SUMMARY option, creating a virtual line below the table (or below groups, if groups are created). And in this summary option, you then choose columns which will be summarized and the type of summarization (sum, average, etc). Those summarizations always appearing below the specific column.
That way, if we created a Group Aggregate summing a specific column, we can just add a SUMMARY and include that same column in the summary, so user will have an easy time seeing a Group Aggregate at the top, but if he doesnยดt know to what column that number refers, he can see the summary below the column and will know itโs the same value as the group aggregate.
LinkedIn
Twitter
