If you are unable to create a new account, please email support@bspsoftware.com

 

Q: repeatable Cognos components (similar logic as Layout component reference)

Started by Martin Rysanek, 09 Jul 2016 10:41:23 AM

Previous topic - Next topic

Martin Rysanek

Is it possible to reuse Cognos components like reports/tables, prompts, filters, etc. defined them in one report and then use them in another report (concept of objects in libraries)? The similar technique is possible with Layout component reference for simple components like Text Items but it does not work for reports or prompts until I put same query + data source (package) in destination report. Using Layout component reference, one can define repeatable header of all reports in "library" like report and then reuse the header in as many report as he needs. When the header is modified in source report, it is automatically propagated to all following reports, where the header is referenced. Can we benefit from similar logic using more complex report objects/components (e.g. tables, prompts, etc.)?

Solution1: manipulation with XML source of reports

Having XML of reports, it is possible to get XML representation of these objects and transfer it to another reports (XML transformation techniques), so not only object definition will be copies by also data source and query definitions (using XML object access or by regular expression).

Solution 2: using SDK to manipulate with object representation in reports

It should be possible to use SDK API to modify report specification and copy/edit/replace definition of report objects.

Both of these approaches seems to be quite complex, are you aware of more simple and for Cognos developers more convenient of reusing cognos objects/components?

Thank you for comments/recommendations

Martin

Lynn

Report Booklets allow you to reference existing reports: https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.crn_nf.10.2.2.doc/c_nf_reportbooklets.html

Copy/paste of XML for queries and layout objects isn't complex, nor is creating a report that has many elements within that can be used like a template. You can "save as" and then author as needed by adding or removing as requirements dictate.

Martin Rysanek

Report Booklet is fine but not for all usecases ... thank you anyway

Copy/Paste of report XML is not complex for me (but it is for our client). Unfortunately, it does not follow the logic of Layout component reference meaning if source report definition is changed then it has to be copied again to all reports, where it is used. (you know, I am trying to stimulate discussion about the problem)

Having a tool (it could be command line), which would take source report/table/prompt=object definition and replace its usage in all reports, where source object is used (referenced), will be perfect solution of the problem.

Is DRU (Cognos Dynamic Report Specification Updater) capable to make these updates based on request (script execution)? It might be able ... I have no experience with DRU...

Martin