In 10.2.200.10, I created a new Report Style with a BAQ RDD for a BAQ that had parameters (because the BAQ Report Designer doesn’t support setting BAQ parameters, at least it’s not obvious if does). This particular BAQ has a custom GetList post directive to do some additional processing.
When the report is run, it doesn’t fire any of the directives, whether it be pre, base, or post. I even put a exception message in each one and it doesn’t care. Now, if I run the same report without setting the BAQ paramaters using the BAQ Report Designer, it will throw an error in the task that can be seen in the system monitor.
Am I missing something, is this intentional, or does it sound like bug?
Reports are submitted for execution and are then managed by the Task Agent and the Reporting framework. As the reporting framework is internal to the AppServer, it does not call the Business Methods in the same way as an external client would so the Method Directive “touch points” are not hit. Should the reporting framework execute the BAQ in the same way as an external client? Arguable…
Starting in 10.1.600, there are now two types of BAQ Reports that can be created. The older single BAQ type supports Column level filters that can work like BAQ Parameters and are entered on the Report UI. The newer hierarchical BAQ Reports - you can have a single BAQ - does support BAQ Parameters - they get prompted for during report submission.
Have a look at the on-line help for more information.
Thanks for looking into it. The BAQ Report Designer does fire the directives as you mentioned but if you manually create a RDD with BAQ as it’s data source and manually create a new Report/Report Style that uses that RDD, it does not. At least for me it didn’t. I tried this on our 10.2.400 Test Environment too.
So:
BAQ Report Designer(Submitted through Ice.Proxy.Rpt.BAQReportImpl): Supports directives but not BAQ parameters.
Hierarchical Report Style with RDD w/BAQ(Submitted through Ice.Proxy.Rpt.DynamicCriteriaImpl): Supports BAQ parameters but not directives.
I’m not as concerned with the parameters functionality but I am concerned that the logic to get the BAQ results is different.
@Rich what would be the argument that even though the reporting framework is internal, why it should not follow the same pattern to get the BAQ results as the external client? I would assume both BOs that generate reports would be using the DynamicQuery BO to get the data.
