I have a vertical bar chart. The data displayed are based on the selection of a radio; you can see data by either the count or by the duration. There are two universe queries each writing to their own set of cells in the spreadsheet. The data displayed in the chart is based on formula (IF button = A then col A else col B). Each query has a trigger such then when you change the selection the appropriate query refreshes. So far so good, nothing exotic.
What my team has started to see lately is that after you switch between the A and B buttons a few times the data on the chart will disappear when you select B. Sometimes there is a slight flicker of the chart where is looks like it is going to show something but it ends up empty.
We are using Dashboards 4.1 SP2. There is no dynamical visibility on this chart.
Theories, suggestions or winning lottery numbers welcome.
Place a spreadsheet component on your dashboard and map it to the same range the chart is using. Run though your scenario again and see what’s happening to the data the chart is using…
We recently upgraded to Dashboards 4.1 SP4. For a while it seemed like this problem had gone away. The problem is back again. The new twist is that we can’t reliably recreate the problem or predict when it is going to happen.
We have been able to figure out what is happening.
We have 2 queries, each with 2 columns, writing to separate cell ranges. The queries are triggered when the user selects one or the other of the radio buttons for the chart. When the swf is loaded Query is run and it’s data display. When the user clicks the radio button for the alternate view Query A and Query B are both triggered. We can see is from SQL Profiler and that the legend on the chart changes (the 2 queries have different sort orders). What is strange is that for Query B only the dimension column is being populated; the measure column is empty. If the users changes one of the other global filters then Query B will show.
We have tried rebuilding the queries in question. We have tinkered with the triggering logic. We have tried writing to different cell ranges. We have looked at all the other queries we are using and none would be overwriting the range in question.
It looks like there is some sort of timing issue at play here.
(BOB member since 2006-03-01)
(BOB member since 2005-01-28)
If the users changes one of the other global filters then Query B will show.