Most Cognos developers have been confronted with this situation before: A report runs perfectly fine in the Cognos Development or Test environment, but has some sort of issue in the Production Cognos environment. This scenario generally results in the Cognos team asking the question, "What are the differences in this report between the Cognos environment where it works (Development/QA) and the Cognos environment where it has an issue (Production)?".
IBM Cognos and Motio Best Practices Blog
Have you ever needed to update the parameters for a large number of report views? This can be very time consuming in Cognos Connection. For example, imagine a report which expects 15 parameters (normally populated via its prompt screen). Since filling out 15 parameters each time they execute this report is a bit taxing, its pretty common place for users to save report views of this report (to capture all of their parameter selections, and make launching the report much easier in the future).