Tagged with Table_view - Visokio Forums http://forums.visokio.com/discussions/tagged/Table_view/p2/feed.rss Mon, 30 Oct 17 13:59:01 -0400 Tagged with Table_view - Visokio Forums en-CA Idea: Table View-Formatting; Alignments in cells/headers? http://forums.visokio.com/discussion/1300/idea-table-view-formatting-alignments-in-cellsheaderss Mon, 13 Feb 2012 06:52:51 -0500 hgross 1300@/discussions
Thanks!]]>
Table View: Conditional Formatting? http://forums.visokio.com/discussion/1510/table-view-conditional-formattings Mon, 30 Apr 2012 03:38:02 -0400 vijay_chidambaram 1510@/discussions
image

Thanks, Kind Regards, Vijay]]>
Conditional Formatting http://forums.visokio.com/discussion/1042/conditional-formatting Tue, 11 Oct 2011 04:30:09 -0400 p_parry 1042@/discussions Insert column and data on table view and prevent that column from loads http://forums.visokio.com/discussion/714/insert-column-and-data-on-table-view-and-prevent-that-column-from-loads Tue, 19 Apr 2011 14:18:36 -0400 Focus_Media 714@/discussions
The question is if there is any way to fix that data in a way that when we update the data manager we don`t lost the data included by the user.

I explain what is happening. We need to point some of the data using users criteria, for instance valorate the urgency of an actions that must been taken in a scale of 1 to 3. We create a new column in a way user can insert its valoration (we are going to use this valoration to work in another iok file). We fill the new column and save, the problem came when we update the data from the sources because the columns created by users lost the data.

There is any tip or way to block the columnt and don't allow it to be updated.

Thank You
]]>
Table view: "Add new field/record" buttons? http://forums.visokio.com/discussion/970/table-view-add-new-fieldrecord-buttonss Tue, 06 Sep 2011 04:42:02 -0400 steve 970@/discussions
"+" icon to the right of headers

Click => adds 1 field with auto name
Right click => menu (add field, add field with name, add multiple fields, add formula field)

ADDING RECORDS:

Show additional blank row at bottom, with "+" in row header:

Click => adds 1 record
Right click => menu (add record, add multiple records)

e.g.:

Field 1 Field 2 Field 3 ... Field 4 [+]
1 data data data ... data
2 data data data ... data
3 data data data ... data
... ... ... ... ... ...
49 data data data ... data
50 data data data ... data
[+]


Then do away with the prompt on "New file" for numbers of records/fields.
]]>
Idea: Table View - "Go to" shortcut? http://forums.visokio.com/discussion/937/idea-table-view-go-to-shortcuts Mon, 15 Aug 2011 07:16:57 -0400 steve 937@/discussions
Ctrl+G shortcut.

Might also be useful to include a "next matching value" option. You enter some search text, and the table view selects the next matching cell in a left-to-right-then-down direction.

Useful when you're editing and don't want to filter?]]>
Idea: Table View - Field Picker should not hide field names? http://forums.visokio.com/discussion/923/idea-table-view-field-picker-should-not-hide-field-namess Thu, 11 Aug 2011 12:19:56 -0400 tjbate 923@/discussions Idea: Table View - "Freeze panes" ? http://forums.visokio.com/discussion/885/idea-table-view-freeze-panes-s Tue, 26 Jul 2011 03:31:41 -0400 steve 885@/discussions Table View: Difference between Aggregation and Grouping? 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.]]>