Report output rows should change based on report format we choose in Cognos 10

[xyz]

Hi All,

We are using Cognos 10.2.2, database is oracle relational model. We have one requirement where we have to display 100 rows by default in HTML format for a crosstab report, but when we export the same crosstab report to EXCEL, we need to display 1000 rows. I am not sure. can this be achieved.

can you guys please let me know your suggestions/guidance on the same.

Thanks & Regards,
XYZ

[New_Guy]

Hi,
The only way to achieve this is by having 2 crosstabs and settting up the required rows per page in the properties and rendering them based on the report output variable.
Good luck
New guy

[xyz]

Thank you very much for the reply New Guy. I did tried that where I am rendering one crosstab when Run Option HTML is selected, where I have set Rows Per Page property to 100. When Run Options Excel is selected I am rendering the other crosstab whose Rows Per Page property is set to 1000.

Here the user requirement is he will run the report by default using HTML. But only when the output is exported at that time only the whole output should be exported to Excel. Is there a way this requirement be achieved by some JavaScript. 

Can this kind of requirement can be achieved in Cognos, all your suggestions and guidance will be appreciated?

Thanks & Regards,
XYZ

[New_Guy]

Hi,
Are you allowed to use another prompt to select the rowcount for 100 or a 1000? So the user can select it and run the report.
Good luck
New guy

[xyz]

Thank you for the suggestion New_Guy. That mean to say, if we set Row Per Page property to any object in HTML, then we don't have an option to export whole data to Excel. If we don't set Row Per Page property to any object in HTML then all the records will get loaded into Excel. User requirement is he wanted to see some specific set of rows in HTML.

That mean to say, we have to suggest the user to have one prompt which we could specify in the prompt page either it could be value prompt or text box prompt, where we restrict that many rows in list or crosstab object. In this case no need to set any Row Per Page property to any object in Report page. When exporting to excel then everything will get loaded into excel depends on how much Excel can support.

Thank you for your suggestion. Your suggestion is much appreciated :)

Thanks & Regards,
XYZ

[xyz]

Hi New_Guy,

I guess I misunderstood, I tried to pull RowNumber into crosstab rows, which is taking longer time to display row number as the crosstab is pulling large amount of data around 4000 rows, where as chart is embedded in rows of crosstab with master-detail relationship. I don't know, how to filter the rownumber. As the rownumber generates the number dynamically, where I can't filter on rownumber. My crosstab design is something like below, where measures are also embedded in rows.


Crosstab
                                                                           Crosstab Column 
                                                                                 Months
Crosstab Rows
                                                       
Item Chart| Scenario| Locaiton   Measure 1
                                               Measure 2
                                                Measure 3
                                                .
                                                .
                                                .
                                                Measure 23


As per below suggestion, if we give option to the user to only display selected rows from the prompt page, then the report would display only specific selected rows and won't display the remaining rows in the HTML view per page. But we, wanted to get all the rows from database, but only the specific selected rows needs to be displayed per page in HTML. But, we don't want to set Row Per Page property to crosstab, user wanted to display on 100 rows in HTML view per page, when page down is clicked, he needs to see the next hundred rows like that till all the 4000 rows.

Rownumber concept doesn't seems like fit in for my requirement. Am I missing something, if yes please let me know your suggestions or do we have some other approach?


Thanks & Regards,
XYZ