Issue linking a report page to a query

[jonathan.webb@raytheon.co]

Hi all, hopefully someone can help me. I'm getting frustrated with what appears to be an inconsistency in Report Studio. I'm using C10.1 FP1.

I have a report pack with around 30 pages. Many of the pages relate to the current month, quarter or year which I would like to display as part of the report title. I have a query which selects the current month / quarter / year and this cross joins to other queries to be used to filter the data appropriately. This all works fine.

To display the period, I am selecting the query mentioned as the Query for the properties of the Page. Then I can drag e.g. the "current year" data item onto the page header, and it will display '2012' as part of the title (for example). This is working on some pages... but not all. When I link the query to the page and run the report, I get the message as per below. NB. I don't believe there is anything out of the ordinary with these pages, and the failure occurs when I link to the query, not when I drag the data item onto the page. The page also runs fine on it's own, just fails when I run as part of the pack!

Any thoughts?

Thanks,
Jon

RQP-DEF-0526

      QueryReuse: the generated sql is not supported locally.
 
RSV-SRV-0042 Trace back:RSReportService.cpp(826): QFException: CCL_CAUGHT: RSReportService::process()RSReportServiceMethod.cpp(259): QFException: CCL_RETHROW:

[Prerna Chaudhary]

Hi,

Try the following settings in the Query Properties

1. Use local cache : N0
    Processing : limited Local

2.Also try once to turn off the cache from FWM .

3.Make sure in Framework manager you have local processing enabled for your package.

4.Also you can try to cast your data type to the same type.

5.Another possibility must be with joins, check ur joins in FWM.


Let me know if you need any further information.

Thanks and regards
Prerna
-------------------------------------
pchaudhary@infocepts.com
-------------------------------------

[MFGF]

Rather than associating the pages with your query, I would probably use a Singleton pointing to the query in each of your page headers.

Just a thought...

MF.