http://forums.visokio.com/discussions/tagged/text_data_type/feed.rss Mon, 30 Oct 17 12:24:50 -0400 Tagged with text_data_type - Visokio Forums en-CA 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/2580/scaling-text-characterstring-length-limit-per-cells Thu, 05 Jun 2014 05:23:47 -0400 mattyh 2580@/discussions
Thank you, Matt]]> http://forums.visokio.com/discussion/2508/export-omniscope-integers-being-stored-as-text-in-xlsx Tue, 01 Apr 2014 04:54:47 -0400 Master_Chief 2508@/discussions
It is very annoying as it requires a manual text to columns in order to fix]]> http://forums.visokio.com/discussion/2163/import-access-text-ending-in-spacess Thu, 23 May 2013 05:56:37 -0400 chrisamott 2163@/discussions 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/1232/keyword-list Fri, 20 Jan 2012 04:39:12 -0500 sherriff 1232@/discussions http://forums.visokio.com/discussion/1101/exclude-results-from-text-search Thu, 17 Nov 2011 10:35:28 -0500 Paul 1101@/discussions 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!]]> http://forums.visokio.com/discussion/1038/formula-if-with-null-values-in-text-field Thu, 06 Oct 2011 12:44:50 -0400 Focus_Media 1038@/discussions
Steps to reproduce:

Create on new iok with 3 text fields: (Original, ChangedByUser, Formula)

Change field Formula and define this formula:
=IF(ChangedByUser="", Original, ChangedByUser)

If I write some text in the Original column, it should be shown in the Formula Field.

This worked fine until I installed yesterday last version.

Now, the condition (ChangedByUser="") ==> Is always False!!!

I think there are a little bit problem with Null/Empty values in a text field.

Because I didn't find a 'function' like IsNull(Value), i had to change the formula to:

=IF(("" & ChangedByUser)="", Original, ChangedByUser)

And then, it works fine... but I need to change a lot of formulas like this!

I think should be a 'function' IsNull(value) or IsEmpty(value), to avoid this problem.

Regards
]]>