Book Image

IBM Cognos 8 Report Studio Cookbook

By : Abhishek Sanghani
Book Image

IBM Cognos 8 Report Studio Cookbook

By: Abhishek Sanghani

Overview of this book

Cognos Report Studio is widely used for creating and managing business reports in medium to large companies. It is simple enough for any business analyst, power user, or developer to pick up and start developing basic reports. However, when it comes to developing more sophisticated, fully functional business reports for wider audiences, report authors will need guidance. This book helps you understand and use all the features provided by Report Studio to generate impressive deliverables. It will take you from being a beginner to a professional report author. It bridges the gap between basic training provided by manuals or trainers and the practical techniques learned over years of practice. This book covers all the basic and advanced features of Report Authoring. It begins by bringing readers on the same platform and introducing the fundamental features useful across any level of reporting. Then it ascends to advanced techniques and tricks to overcome Studio limitations.Develop excellent reports using dimensional data sources by following best practices that development work requires in Report Studio. You will also learn about editing the report outside the Studio by directly editing the XML specifications. Provide richness to the user interface by adding JavaScript and HTML tags. The main focus is on the practical use of various powerful features that Report Studio has to offer to suit your business requirements.
Table of Contents (18 chapters)
IBM Cognos 8 Report Studio Cookbook
Credits
About the Author
About the Reviewers
Preface
Index

Version controlling


Cognos allows direct connection to certain version controlling software (Visual Source Safe being the most popular) for Framework Manager. However, there is no direct mechanism for the reports.

The following methods are seen in different organizations for Version Controlling of the reports:

  • Copy the report specification to clipboard, save it as an XML file, and store it in the version controlling system.

    • This method allows easy comparison to prior versions of the report, and hence is good for code review during any changes.

    • However, it can be tedious. Also, restoring to older version needs to be done one report at a time. This also breaks any existing report views defined at the target location.

  • Export the whole suite of report and store the export file (ZIP format) in the version controlling system.

    • This is less tedious than prior one as only one file is created for whole suite of reports.

    • Reverting back to an older and stable state is easy. (Entire suite is reverted back so you can bring the system back to older and stable state – like baseline)

    • However, this method is not particularly useful while troubleshooting a report to check what changed in it over the versions.

  • Use of third party tools.

    • It is possible to hook up to the content store to retrieve the information. There are some third-party tools available that use this method to retrieve report specification and do certain jobs.

    • You can consider the tools like MotioCI to automatically record the report versions and track changes. They also allow you to revert to older versions. (More information can be found on: http://www.motio.com/products/ci/overview.do)