http://forums.visokio.com/discussions/tagged/category_data_type/feed.rss Mon, 30 Oct 17 12:14:29 -0400 Tagged with category_data_type - Visokio Forums en-CA http://forums.visokio.com/discussion/3240/value-order-for-text-fields-filter-ordersorting Wed, 10 May 2017 06:08:55 -0400 luukvanm 3240@/discussions
What is the basic sorting for an filter? A customer of us wants to have the filter ordered alphabetically, I have found the option in the attachment to fix the ordering. But I was wondering, if a new value will be added to the filter, will this also be alphabetically sorted or will the new value be added at the last position in the filter?

Thanks,]]> http://forums.visokio.com/discussion/3252/category-field-data-type-consistency Mon, 19 Jun 2017 12:53:43 -0400 bernardpi 3252@/discussions
We are testing some reports against multiple data sets with the same structure (same fields) but different data points and believed that the "category" field data type applied to fields with a certain number of discrete text values (under 500?) - however, we are finding inconsistencies in the way these are interpreted with some fields being read as data type text and others data type category. We are querying from an ingres database if that helps.

Is there a way to guarantee the output data type value that then ultimately drives that type the filter is? Like some rules to follow? (Selectable options as opposed to text search boxes). We are finding that selecting category data type on the field is not enough if the data points underneath change.

Thanks for your help in advance]]> http://forums.visokio.com/discussion/1506/pivot-view-date-time-fields-and-top-5-text-categories.- Fri, 27 Apr 2012 01:53:12 -0400 rajeshbalu29 1506@/discussions
I have a requirement of creating a pivot with x-axis as months - MMMyy and y-axis by top 5 Categories. Currently, the Pivot View is only supports aggregation by Text Category, but if I convert the MMMyy from Date/Time to Text Category, then it does not automatically sort them properly (chronologically)?

Also I need the same feature which we had in the Bar/Line View restricting only top 5 Text Categories in the Pivot y-axis view?

Regards, Rajesh B]]> http://forums.visokio.com/discussion/2157/outputs-batch-pdf-category-fields-reverting-to-texts Tue, 21 May 2013 10:18:11 -0400 Ed_Roberts 2157@/discussions
Is there a way around this (without presumably having to firstly batch output to IOK and then create another step to convert to PDF ?

Thanks, Ed]]> http://forums.visokio.com/discussion/1519/preserve-category-colours-from-changing Wed, 02 May 2012 09:57:32 -0400 Julia_OIS 1519@/discussions http://forums.visokio.com/discussion/1498/prevent-category-colors-from-changing Wed, 25 Apr 2012 04:22:30 -0400 Patricia 1498@/discussions
I made some changes to the category-colours for my category-field by editing the colours in the menu:

Data > Manage fields > Options > Value order, colour


Now, by editing the category-name later, the colours are changing again. Also by simple refreshings for the data, all of my colouring work is gone and the colours changed again.

Is there a way to "save" my edited colour-settings for the categories?

Thanks for your help in advance.

Best Regards
]]> http://forums.visokio.com/discussion/1078/what-are-the-rules-for-flipping-from-category-to-text-data-types Tue, 01 Nov 2011 12:01:14 -0400 Guy_Cuthbert 1078@/discussions
Most long-term Omniscope users will be familiar with the similarities and differences of Category and Text data types. Most, I'm sure, will have experienced the odd headache when defining a Category field, and then 'over-filling' the Category with "too many" entries so that Omniscope decides it should be held as Text. Some will have experimented with various technical/advanced settings to try to control this.

At present we have 3 separate (but related) situations where this *appears* to be the case (i.e. a Category field is forced to become a Text field), but we're struggling to identify the exact cause. Ideally, we would like *absolute control* (in a Field Manager block, in DataManager, preferably) over a field's data type - and we're happy to take the consequences (e.g. a flaky IOK file!). In the absence of such control, it would be *very* helpful to understand the 'rules' that Omniscope uses to make this decision - this way we may be able to protect against it.

So, the cases we have identified are:

1. Too many separate values in the Category
We're all familiar with the warning ("you have more than 500 entries...") which Omniscope displays when a user converts a Text field into a Category. We can override this (by accepting the risk), but we have experienced cases where refreshing a model with new data causes Omniscope to reassess this risk, and convert from Category to Text.

2. Too long a text value / too many long text values
We're not exactly sure of the 'rule' here, but we have documented cases where a Category field with only 10-20 entries is converted to a Text field, and this seems to be where individual field values are long i.e. LEN([FieldName])>100 (or 200?). It may even be some form of aggregate, where more than 5 entries of more than 100 characters force the switch to Text?

3. Dynamic content from a Formula
We have cases where the content of a Category field is switchable according to a Variable setting i.e. a formula like:
IF([Variable]="X",[CatFieldOne],[CatFieldTwo])
We can define the formula field, and the two source fields, as Category data type... and both the 'source' fields (CatFieldOne and CatFieldTwo) remain as such, but changing the Variable value - and hence altering the content of the formula field - causes Omniscope to 'reasses' and flip to a text data type.

I would be interested in:
* Anyone else's experiences of Category to Text conversion - are there other cases I haven't identified?
* Visokio's summary of the 'rules'
* Any workarounds that people have discovered
...
* and a nice, simple solution from Visokio :)

Thanks!]]>