Export to excell does not work for wide reports.

[CognosTalk]

Export to Excel does not work for "landscape" or wide reports.
Other reports export nicely to excel or pdf, but some of my reports are extremely complex, they execute fine in html, then when trying to export to excel it executes forever, never exporting anything?
What can be the problem?
Thank you in advance for your reply.

 

[almeids]

When you say they execute "fine in html", you can click on last page and the run time is reasonable? Html initially returns one page of the report while other formats must run it to completion. I'm guessing you would have the same issue with pdf output...try it and see. If pdf runs OK too, provide more details about the complexity you mentioned.

 

[CognosTalk]

Thank you for your reply,
You are absolutely right, i cannot export this report to pdf, i can go to the end of the document but this report is not long.
I was wondering if i can attach the report itself to your info, maybe you can suggest something; i have a lot of queries and joins.

 

[almeids]

Not sure what you mean - if you mean posting your report here, that won't do much good since I don't read xml and I doubt your database or FM metadata look exactly like mine.
So, some generic advice:

- "A lot of queries". First, can you reduce the number? Are you hitting the database more than once for the same info when you could be using tabular references? (sorry if you're Cognos 8, I only know ReportNet terminology - we are talking about one or the other here, I hope) Second, step through all the queries in your report and run each tabular model individually to see if you can identify the source(s) of your performance problem.

- "A lot of joins". Are these joins in FM, or are you joining with filters/tabular children/tabular references in Report Studio? Local joins which are not modelled in FM can be performance killers.

- Are your database tables indexed? Are they indexed on the things you are filtering on? Both answers should be yes. Try running the Report Studio generated sql in your database client to see if the bottleneck is there or in ReportNet.

HTH

 

[CognosTalk]

i do have outer joins between the queries, and now trying to illuminate them.
the database is perfect, report specifications are complex, I need a separate query for each column of the query, since each column represent different data mart.
How come it executes well in html and export does not work?

 

[stewm]

Have you found a way to render your Excel in landscape?

Mark Stewart
Business Intelligence Consultant
Consultants Club Corp.
Windsor, Ontario
Canada

 

[CognosTalk]

I fixed some of my reports, the problem is the query.
some unions, i just switch the place of the query, like 2 put as first then all of the sudden it exports. Another report asked for local processing, i set local processing for this specific query in the report and it exported.
What can it be?
Now i am facing 4 more reports, that do not export to excel, they execute fast and successful in HTML, very complex, one have a union, where have value on one query and do not have in another,+ i am converting, not sure how to re-write it!
Any suggestions will be appreciated!