Custom SI7 Reports only run against 1 ACD

[Sandman83]

Hi Everyone,

I have written a report with Seagate Info using Aspects container reports. For some reason when I run the report, anything that references anything in the container report runs againast the selected ACD, but anything in the subreport will only run against my local ACD (which is the one I used to build the info view).

I tried rewriting it the same way Aspect writes their reports, writing the pass-through queries (which run fine from within Access), making an info view based on the new query, writing a subreport based on the new info view, and referrencing the query in the query exacution formula in the container report.

When I run that report I get nothing. No information, no errors, nothing. Just the text fields that were put in the report.

Anybody have any ideas how I could fix either one?

Thanks,

Tim

 

[CmdrGravy]

I have noticed a similar thing in Seagate myself when I have tried to modify the standard reports.

It seems like one of the reasons Aspect use the pass-through queries is to enable you report on different ACD's using the same report.

For this to work I think you need to point both the container report and the sub-report to the Access Database.

The container report uses that little function in the details to generate a new table in Access based on the Template query.

You'll notice each query e.g. AppsDetail has a matching AppsDetail_Template ( or something like this ). The function in the detail of the container report creates a new query using the name of the actual Oracle DB you want to report on so the AppsDetail table referenced in the sub report has been refresed and contains the latest info using the correct ACD.

I think what you may have done is create a new query but not a new query_template ?

If you don't do this then whatever ACD you base the sub report on in design will remain the ACD it reports on ever after.

This is a little confusing ( and I may well be wrong about this ) since when you schedule the report it gives you the Database Login tab which seems to imply you can enter the name's of different ACD's in here. Maybe this is the case and I'm doing something wrong but in reports I design myself it doesn't matter what I put in here it runs on the original database regardless !

 

[Sandman83]

Thanks for the reply CmdrGravy,

I actually received a call back from Aspect support and was explained why Aspect uses the pass-through query and how it works with Seagate.

I had built the template query, and even the OV query that we never use. The problem I had was I built the info view against the call center and not agianst the query. Once I built a new info view against the query and built a new subreport against the new info view, it worked fine.