I may be misunderstanding the way dial charts worked but here goes.
I created a dial chart (not %) just a regular dial chart.
my query was : select count(*), 200 from mytable; -- just counting number of rows (always less than 200)
So when the query return 40, my chart shows 40. But when the query is returning 0, my dial won't go below 2.
So I tried modifying query to select count(*), 200, 0, 200 from dual; Same problem.
And here it gets weird. I went into the query section of apex and changed my query (note, I did not create new dial, just moded old one) to
select 0, 100 from dual;
I still get back a value of 1 on the dial.
Anybody seen anything like this? It's like some weird uber cache somewhere or something. I can't figure it out.
So we did the following :
select 0, 20 from dual; -- shows 0
select 0, 100 from dual; -- show 1
select 0, 200 from dual; -- show 2
select 0, 500 from dual; -- show 5
Is this a bug?
Edited by: user3932435 on Aug 11, 2010 7:28 PM
Thanks for bringing this issue to my attention. It appears that you have hit some behaviour that's reproducible in our Flash 3 charts as well as our Flash 5 charts with APEX 4.0. I believe the reason that it wasn't apparent before now, with the Flash 3 charts, is because there was no option to display a value on the gauge pointer with the earlier charts. With APEX 4.0, we've extended the Chart Attributes to allow for the display of the value. Obviously in your case, the incorrect value is being displayed and will be misleading to your users. I appreciate this is not ideal, but if possible I would suggest updating your attributes to switch off the display of the Value on the gauge. I will address this in a future release, as with the exposure of the "Value" attribute with Flash 5 charts, we don't want to be displaying incorrect information. Thanks again for bringing this to our attention, and hopefully by switching off the Value attribute, you can still proceed with your use of the gauge chart.
Thanks for the response.
Our clients are sharp and immediately noticed that the dial is still pointing to the value of 2 (even though the value is not displayed as you suggested).
Can you give me an idea as to the timeline for a solution to this issue. If it's weeks we can hold on, if months, then we will have to choose a different chart type and modify the report.
To be honest, I cannot give you an exact timeframe right now, so my suggestion would be to revert to a different chart type for the time being. Again, I appreciate this isn't ideal, but we will address this in a future release.