http://forums.visokio.com/discussions/tagged/data_typing/feed.rss Mon, 30 Oct 17 16:29:00 -0400 Tagged with data_typing - Visokio Forums en-CA http://forums.visokio.com/discussion/2908/performance-tab-taking-too-long-to-loaddisplays Wed, 15 Apr 2015 12:03:10 -0400 Alexander 2908@/discussions
For one of our clients we developed a dashboard. The dashboard has a limited dataload, yet the performance is less then we expected. Tabs are taking several minutes to load, and filterings need more time to load as well.

I would like to know what the cause is of this lack of performance. Hope you can help me investigating this issue.

Thanks!]]> http://forums.visokio.com/discussion/2746/filtering-category-field-in-desktop-shows-as-text-field-in-web-start-viewers Mon, 20 Oct 2014 14:15:08 -0400 Alexander 2746@/discussions
We publish a dashboard to one of our clients using a template that we save elsewhere using the Scheduler. In the file action we have the following steps:
- Refresh from source
- Unlink from source
- Save IOK

In the source file the field is a Category type. In the template the field is also a Category field.
After the Scheduler action I opened the saved IOK file, and the field is (as expected) a Category field.

However if we deploy the same file using Web Start, the Java free Viewer opens to show the field as a Text field with an "search text" filter option.

This behaviour seems to be new, but I am not sure since when. How can we show this field as a Category filter even when we deploy in free Viewer using Java Web Start?

Please advise. Thanks

Regards!
Alexander]]> http://forums.visokio.com/discussion/2544/formulae-text-processing-determining-text-or-numbers Thu, 01 May 2014 08:23:16 -0400 aknotts 2544@/discussions
TYPEOF(value(left([my_string], 1)))

This returns the type of the argument passed to it (e.g. text, decimal, integer)
]]> http://forums.visokio.com/discussion/2515/data-type-integer-date-or-category Mon, 14 Apr 2014 15:34:38 -0400 TomRiggs 2515@/discussions 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/2300/versions-2.7-category-fields-re-typed-text-numeric-or-date-fields-in-2.8s Thu, 29 Aug 2013 06:38:17 -0400 Alexander 2300@/discussions
We are upgrading to 2.8. So far we have not encountered any problems in data-flows. We have seen some new features, looks really good. Now we are publishing our 2,7 build dashboards with the 2,8 scheduler. The process works fine, but the field types in the dashboard are not what we expected. Category field have become text, numeric or date fields.

After investigating this issue the problem also occurs when opening the dashboard in 2.8.

Is this the expected behavior?

(using 2.8 b1088)]]> http://forums.visokio.com/discussion/1981/data-typing-text-vs-categoriess Thu, 10 Jan 2013 20:54:08 -0500 shaji_o 1981@/discussions
However there a some instances where "List of categories" doesn't appear as an option under filter type. Is this because there are too many values for a check box? ]]> http://forums.visokio.com/discussion/1896/barline-view-sorting-bucketed-numeric-datas Tue, 13 Nov 2012 11:24:10 -0500 earheart 1896@/discussions http://forums.visokio.com/discussion/1801/barline-view-display-7-previous-weeks-in-reverse-orders Mon, 01 Oct 2012 06:29:49 -0400 kgurus 1801@/discussions
Details are here:
Split by: Week (Integer) Bar: Metric 1 Line: Metric 2

So ideally, I would like to define a subset of the data to be shown in the view to the contain the data of current week and also the previous 7 weeks.]]> http://forums.visokio.com/discussion/1263/updated-data-in-database-table. Mon, 30 Jan 2012 02:28:21 -0500 naruemon 1263@/discussions
I used Database table as the source. Will Omniscope detect automatically for the new/updated data in DB?
Or do we need to update ourself? Please suggested

Thanks :D]]> http://forums.visokio.com/discussion/1162/summary-and-granular-level-data Mon, 12 Dec 2011 12:15:52 -0500 adam_varney 1162@/discussions
Sorry if this is not the best explanation for the issue but any help with gettining this data to the correct format would be appreciated

Thanks
Adam,]]> 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/773/grouped-data-on-network-view Mon, 16 May 2011 11:28:10 -0400 slaterm 773@/discussions http://forums.visokio.com/discussion/623/define-a-field-as-a-category-in-field-organiser-block Wed, 26 Jan 2011 05:14:36 -0500 edtclarke 623@/discussions
We would really love the ability to force a field to a category in the field organiser block in DM. We have had some mixed results trying to force the data into an explorer/omniscope block and changing to a category there.

Thanks]]>