Pie chart - Duplicated values on data points

[#1]

Hi all,

I'm creating a pie chart with de values on data points inserted.

However this values are duplicated in each next slice as you can see below.

Does anyone know how can I get just the corresponding values of each slice?

The .qvw example file is attached if it helps.

Many thanks,

PL

[SunilChauhan]

but in your attachedment showing only one value?

or something else you want

[#3]

I see the graph on my desktop as it is in the picture.

Is it possible to be a machine problem?

How can I fix it?

Thanks,

[SunilChauhan]

close and open application again.

or create chart again

hope this helps

[#5]

Already tried that...

Still doesn't work...

[Nicole-Smith]

I've been getting the same thing since upgrading to QlikView 11.  The charts that I have look correct in QlikView 9 and QlikView 10, but when I open them in QlikView 11, that's what they look like.

[#7]

Hi,I used to get this problem in the tooltip for pie charts. This is how i fixed it : Properties->expressions-> Display options - deselect the text as popup option. It fixed the issue. May not work for your issue but I guess you'll find your solution in the display options itself.

[swuehl]

Seems like a bug to me, at least versions 10 and 11 behave differently and I can't see a way to get the single numbers back in QV 11 SR1.

If you are a QV customer with a valid support contract, you can report this issue to QT.

edit:

I think the issue arise from the use of multiple expressions instead of a dimension and 1 expression. There seems to be a bug using multiple expressions and display options 'values on data points' in QV11.

You can maybe workaround this by using a dimension and only 1 expression, i.e. by transforming your table from a crosstable type to a straight table type (using CROSSTABLE load prefix in the script). See attached for a sample.

Regards,

Stefan

[ToniKautto]

This is a known issue and has been registered as a bug with id #46123.

[ksmith24]

Does anyone know if this bug has been resolved?  It seems to still be occurring, at least in 11 SR2.