Hi,
I've found a couple of issues using the date picker in a report and on dashboards. One is easy to explain, but the other has less consistent behaviour.
Easy one first!
On a 'Graph only' report using a date picker to select an @PARn@ based filter value, if the graph is too wide the date picker will be partially covered by the graph. The graph width at which this becomes a problem will depend on the report and the resultant position of the @PARn@ date field. In the example below it is the only @PARn@ field, with a graph width of 700px. Reducing the width to 500 px removes the overlap. The machine list selection is not covered by the graph when it is activated.
The more difficult date picker problem involves inconsistent behaviour when selecting a date which is used as a filter on a dashboard. I have constructed a couple of dashboards which are made up of four reports, all of which use a date picker to select @PAR1@ used in their underlying Dynamic SQL Views. The 2nd filter for each of the reports is a machine identifier selected from a report list. Date and machine selection work fine within the individual reports .... but date selection is inconsistent within the dashboard.
Sometimes it will appear to work consistently. Then, if another report is run prior to returning to the dashboard it will no longer function. On other occasions it just won't work at all. Basically, it either works fine ... or the date picker simply doesn't appear at all. And, once it fails to appear it continues not to appear in that instance of the dashboard. As I mentioned above ... hard to describe ... and a bit confusing as a user. End result is that the date picker can not be relied upon to appear.
Below is a dashboard with date picker working fine:
and then not working at all:
I've tried to identify any particular conditions that might be leading to the problem, but so far without success. What I can say for certain, is that when the date picker fails to appear the browser page indicates 'Error on page'.
I'm hoping someone else may be able to replicate the problem I'm seeing. Is there any way of finding out what the 'Error on page' is?
Regards,
Greg Shearer