From the midtier, using the ReportSelection form works fine, with a
caveat. If a report (created with the ReportCreator form) has a query
that contains arithmetic such as 'date_field' > $\DATE$ - 60 * 60 * 24 *
10, the report returns nothing (no error message, just blank). However,
queries without calculations such as 'date_field' > $\DATE$ or just
'date_field' > (some_number) work fine. Does anyone know of a work
around for this? I've submitted an issue as well, but there appear to
be multiple open issues with qualifications and the ReportSelection form.
The strangest part is the WUT doesn't use the qualification at all, but
the midtier does (with the aforementioned caveat). As Chuck Baldi
discovered last year, the "Run" button AL opens a window report with a
qualification of EXTERNAL($query$). However, the $query$ field is blank
and has no workflow associated with it (it is always blank!). And yet,
somehow (magic?) the midtier can run the report with the qualification,
presumably executing the same AL. If I implement the workaround Chuck
created (set the $query$ field), the WUT runs fine with the
qualification in effect, even with date calculations! Progress? No:
this same work-around BREAKS the midtier even more for queries that use
keywords such as $DATE$, etc, because those are stored as the internal
representation such as $\-4$, which the midtier doesn't understand. I
am trying to fix it with the application-parse-query process commands
but having difficulty since those only run as filters not as ALs.
Thanks for any advice!
Brien
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
