Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When creating a pie chart in Qlikview with data values being shown for each pie slice, when I mouse over a slice, it expands the slice which is great but it also expands the data value; but does so using a duplicate on top of the original, resulting in the following issue:
Obviously this looks very sloppy, however I need the data values visible as a default because having them mouse over for each segment is a waste of time and putting the data in a chart below deparates it and makes it tougher for them to easily and quickly interpret the data.
Honestly, this is just one of a slew of Qlikview graph visualization issues that I've discovered over the past few weeks (although I've found less info on this issue, so I may just be missing a button or checkbox somewhere). It makes me think that Qlik is very sloppy in this area and has abandoned Qlikview default visual improvements so that they can focus on Qliksense, even though they said they would work on both at the World Conference, but this doesn't seem the case; and unfortunately Qlik Sense isn't appropriate for a large number of Qlikview users for a variety of reasons. Anyway, enough about that, does anyone have a fix or workaround for this?
Hi Richard,
Hope you are using prior QV version 11.2 SR4 .This is a bug and it is corrected in QV 11.2 SR 4. Check the bug id 63230 in the attached release notes.
Actually I'm using 11.2 SR9, so the bug still exists....
Perhaps it's corrected in SR12, but it doesn't make sense that they would correct it in SR4 and it would happen again later on. Should I submit this somewhere?
Hi Richard,
I just came across another thread similar to the issue faced by you here https://community.qlik.com/thread/52555
Since you are using the bug fixed version and still facing the issue, better to log an issue with Support team. May be here Qlik Support - Business Intelligence (BI) Reporting Software Solutions | Qlik
Let us know once the issue is resolved or share the troubleshooting steps if they recommend to you.
Regards,
Siva
Nevermind, it was fixed once more in SR12, which i just updated to.