http://forums.visokio.com/discussions/tagged/grouping/feed.rss Mon, 30 Oct 17 16:29:03 -0400 Tagged with grouping - Visokio Forums en-CA http://forums.visokio.com/discussion/1949/idea-table-view-sorting-grouped-valuess Fri, 14 Dec 2012 04:25:49 -0500 acohen 1949@/discussions
At the moment, if you sort on a field that is Grouped, the sort occurs at granular un-grouped level and hence is not useful for the end-user. I find that I hardly ever use the grouping functionality because of this.

Can we make it so that when you click on a column that is grouped the sort occurs at the grouped level and then when you expand the table (and click again) the sorting will then occur at the expanded level?

This functionality, although simple, would make a massive difference in terms of usability and report design impacting on almost all of our reports.

Thank you,]]> http://forums.visokio.com/discussion/2822/display-display-two-tables-with-different-groupings-expandeds Wed, 21 Jan 2015 04:16:05 -0500 enrico68 2822@/discussions Since expanding all categories will result in a wide table difficult to be read when printed, I created, copying the first one, a second table equal to the first one as indicated in Figure 2.

The idea was to expand some of the groups on the first table and the others on the second table (in this way in both tables it is possible to read the total of each category - expanded or not - and the overall total).

Unfortunately it seems almost impossible to do this because when I choose the groups to expand on the first table, these are expanded also on the second one and when I change the expanded groups on the second table, these are expanded also on the first one.

The only way I was able to obtain two tables with different expanded groups was to change the order of the columns in one of the tables (as reported in fig.3 and fig.4). But if I return the copied table columns in the same order of the original table, the order 'magically' change again and the table return equals. Also changing the order of the original table as in the copied table, results in a grouping change.

So the question is: how to get two equal independent tables in one Omniscope .iok?]]> http://forums.visokio.com/discussion/2752/export-grouped-table-view-data-to-excels Sun, 02 Nov 2014 14:06:51 -0500 kmatrix999 2752@/discussions
I have grouped and filtered data in table view. I have tried to export the data to Excel but lose the grouping.

Is there a way to export data to Excel and retained the grouping and sub totals?]]> http://forums.visokio.com/discussion/2374/versions-2.7-to-2.8-server-transition-issue Mon, 14 Oct 2013 05:27:34 -0400 DominicChan 2374@/discussions
This makes the correctly grouped table in 2.7 to display incorrectly after being saved down through the server.

Can you advise if this can be rectified in later versions of 2.8?

Thanks
Dom]]> http://forums.visokio.com/discussion/2316/table-view-grouping-options Fri, 13 Sep 2013 05:33:36 -0400 davedunckley 2316@/discussions
I don't seem to have any option of fields to Group by in Table View. Any reason why this might be?

Thanks, Dave
]]> http://forums.visokio.com/discussion/2113/table-view-sort-by-grouped-totalss Mon, 29 Apr 2013 11:30:13 -0400 Mees 2113@/discussions Sorting a column in a grouped table works not as expected... it sorts the underlying records (I assume).
We would want sorting the values you see in front of you, the totals...?

Thanks, A]]> http://forums.visokio.com/discussion/1892/table-view-sort-by-grouped-subtotalss Sun, 11 Nov 2012 10:52:51 -0500 Alexander 1892@/discussions Am I doing something wrong or is this not possible? Thanks!]]> http://forums.visokio.com/discussion/883/table-view-improve-table-view-grouping Tue, 26 Jul 2011 03:26:56 -0400 steve 883@/discussions 1. formula calculation precedence options should mirror aggregation (formula result per field, rather than view-wide precedence setting)
2. wysiwyg, i.e. you have to show fields for them to work in formulas precedence setting (because otherwise you can't configure the mean/sum function for hidden fields)
3. you can currently only group by category fields
4. you can't show summaries in blank collapsed grouping columns
5. memory-inefficient

Ideas: improve the options so it is identical to aggregation, except the aggregation fields are in a chosen order, and you can expand/collapse them, and sort the resulting data.

Or, consider merging aggregation with grouping, by making aggregation have the collapse/expand capabilities currently only available with grouping.]]> http://forums.visokio.com/discussion/1088/menus-formula-and-aggregationgrouping-interaction-2.7- Wed, 09 Nov 2011 06:12:14 -0500 steve 1088@/discussions
These ideas would not affect pre-configured IOK files; they would only change default settings, and hide inactive unusual choices.

1. In the function picker, only show functions which have the same resulting data type (in the same "logical value domain") as the field they are applied to.
   
   Visible choices (depending on field data type):
   
   • Sum
   • Mean
   • Median
   • Mode
   • Minimum
   • Maximum
   • Singleton value
   • First value
   • Last value
   • (Formula result)
   
   
   Power-user hidden choices:
   
   • Record count
   • Empty count
   • Non-empty count
   • Unique value count
   • Unique values list
   • Range
   • Standard deviation
   
   
   You would still be able to get at the power-user hidden choices easily but would not see these by default.
   
   This is necessary for (3), to avoid aggregation/grouping from changing the data structure and preventing formulas from working. Formulas are defined to operate over underlying raw data, and if your aggregation changes a text field into a numeric through the use of "Empty count", the formula will most likely fail.
   
   This change would occur in grouping and aggregation, but perhaps also elsewhere for consistency and to remove choices which are confusing - e.g. a value labelled "Sales volume" but showing "Range" is incorrect.
   
   
2. In the Table view, we provide a "Formula result" option for each field alongside sum/mean/etc., just like with aggregation, instead of the "calculate formulas over grouped results" precedence setting.
   
   
3. In aggregation and grouping, we make "(Formula result)" the default for any formula field. This would include the Table view grouping, in-view aggregation, and the Aggregation operation in the Data menu and in DataManager.
   
   Note: While the bar view aggregates automatically, we couldn't allow choosing "Formula result", since Omniscope couldn't tell whether to sum/mean/whatever in any fields referenced by formulas. Instead, you would use the new "Formula" measure in 2.7, which allows you to write your own field-independent formula where you are required to use SUBSET_SUM/MEAN as appropriate.
   
   

This would mean that, if you have formulas configured in the underlying data, and you are rolling up a view to show the total sales per region, your formulas would re-execute by default.

However, due to the power and complexity of formulas, we would like to get feedback from our power users as to whether this would be a net-positive change. Would it reduce the incidence of incorrect configuration, for common models? ]]> http://forums.visokio.com/discussion/773/grouped-data-on-network-view Mon, 16 May 2011 11:28:10 -0400 slaterm 773@/discussions http://forums.visokio.com/discussion/19/table-view-difference-between-aggregation-and-groupings Thu, 04 Dec 2008 09:06:39 -0500 Guy_Cuthbert 19@/discussions
Aggregation allows the Omniscope to work on a reduced data set - so the chosen view (including a Table View) is displaying a different set of data - whereas Grouping is a means of hiding or revealing some of the rows in the data set. It is quite possible to use both techniques together to hide/reveal (Grouping) summarised data rows (Aggregation). The essential difference can be though of as this:

* Aggregation is a data-level summarisation technique which causes data to be summarised before it is presented to the user in one of many views
* Grouping is presentation-level Table View (only) summarisation technique which allows rows to be "rolled up" to a summary level and then expanded by the user to get back to the underlying detail in the Table

When data is aggregated, Omniscope will combine rows based on the options selected - typically this is used to create a summary level of data which can then be manipulated as if it were the base data set in Omniscope. The user selects one or more fields to aggregate by, and Omniscope generates a summarised data set where the values of the selected fields are retained, but all non-selected fields are either ignored (shown as an aggregation value of none) or summarised in some manner (e.g. sum, mean, maximum etc.).The resultant summary data set can be manipulated in Omniscope exactly as if it were the base data held in the Omniscope IOK model. For more information on Aggregation search the FAQ for additional examples.

Grouping allows the user to "roll up" rows within a Table View and then "drill down" into detail within the rows. Grouping is a presentation-level technique and, as such, alters the way in which Table View data is displayed. Once Grouping is active, on one or more fields, Omniscope places an expansion arrow next to each summarised row to allow the user to expand the rolled up row and see the individual data rows beneath (subject to the Grouping > Settings > Expandable tree options being ticked). Grouped data cannot be sorted (the underlying rows are sorted, but not the grouped totals) which can cause confusion - if you need to sort columns of summarised data then use Aggregation.]]>