http://forums.visokio.com/discussions/tagged/decimal-display/feed.rss Mon, 30 Oct 17 17:53:12 -0400 Tagged with decimal-display - Visokio Forums en-CA http://forums.visokio.com/discussion/2709/table-view-aggregated-fields-decimal-place-displays Wed, 10 Sep 2014 06:35:45 -0400 triptiagarwal 2709@/discussions In a Table view if I aggregate it to one column and for all other columns I am calculating the mean, can I restrict the result to only two decimal places? As of now it is showing mean value up to 6 decimal places.]]> http://forums.visokio.com/discussion/2601/display-displaying-full-15-decimal-place-accuracys Tue, 17 Jun 2014 11:05:45 -0400 acdewinter 2601@/discussions
I've run into a serious problem when working with numbers/decimals in Omniscope when pulling the data through SQL Server.

I was a little perplexed when I was dividing a large number by 100 and it kept rounding the output to 1 decimal place instead of two. So I went about making sure I use Convert(decimal) as well as Round to ensure I get both decimals. However it kept only returning the single decimal in a rounded format. I then tried several different data types and still sat with the same problem.

So I decided to run some tests by just doing my own calculations instead of pulling out specific fields (in case this was a DB problem)

A simple calculation of 100/3 which should return 33.3333333 returns only 33. So I converted both numbers to decimal and it returned: 33.33333
Success!

Then why did I still have a problem?

So then I tested 1000000/3 and low and behold it returns 333333.3 (only one decimal) and no matter what you do to it, it will not return a second decimal or more.

So then I tested 10000000/3 and it returned absolutely no decimals, which then lead me to the conclusion that you are limited to 7 characters when working with decimals in omniscope.

The size of the integer can keep increasing but you can't have decimals when it exceeds 7 character length.

I have attached a screenshot for your viewing to illustrate what I mean.

Please could someone help me with this, as the data I'm working with needs to be accurate to the decimals I specify.

Just incase someone suggests this: using Cast instead of Convert makes no difference, and infact works even less.

Edit:

I see another colleague has brought this up previously around aggregation blocks: http://forums.visokio.com/discussion/2437

It seems even with SQL it does retain the precision and you don't require to run conversions on all the individual parts. I just popped a field organiser on and it seems to work.

Maybe a suggestion going forward would be for you guys to add in a option to use/not use this function on a datasource and an option for the user?]]> http://forums.visokio.com/discussion/1964/dial-view-decimal-place-displays Fri, 28 Dec 2012 05:33:23 -0500 s_daffern 1964@/discussions
Thanks - Ste]]> http://forums.visokio.com/discussion/1591/decimal-place-question Mon, 11 Jun 2012 09:31:52 -0400 alec_webliquid 1591@/discussions
Question for the Omniscope team: when setting the number of decimal places for a field, is the field value stored with that number? Or is it stored with the full number of decimals (however many that may be), but displayed with the amount set (similar to Excel)? I ask because I have noticed some small discrepancies between values calculated live in a table view (formula result on aggregated data) and values I have calculated elsewhere from the raw data, in a single function call.

Many thanks!

EDIT: it is of course entirely possible my formulas are not quite correct, but the question still stands]]> http://forums.visokio.com/discussion/98/idea-100-stacked-bar-graphs-decimal-places-in-labels Wed, 01 Apr 2009 16:59:33 -0400 andy 98@/discussions I use 100% Stacked Bar Graphs to analyse performance in terms of market share. Is there any way to increase the number of decimal places in the percentage labels in these graphs?

Currently the report shows zero decimal places, however, if a certain suppliers value share of the market shows growth year on year from eg 8% to 9%, this could in fact be 7.5% to 9.4% ie a true growth of 1.9%, not 1%, which is very misleading due to the rounding.

If anybody could shed any light on increasing the number of decimal places in 100% stacked graphs, I would be very grateful. Thanks.]]>