Strategies for replacing productive reports?

[hespora]

Hi there,


so I have a report that's running productively, being called by roughly ~100 jobs, all with their own saved values for parameters.

This report needs updating. Development will take a longer time than the interval of the report runs (let's say the report runs every day, and I will need 3 days to make all the changes and get everyone's signoff on the new version).

Obviously, its not a good idea to simply save a changed, but not finished report of which I know it would be run the next day. So I'm saving a development version until I'm finished and ready to deploy that report.

How do I actually go about deploying the new report version? If I use "save as" to overwrite the productive report, this would result in broken entries in existing jobs. Opening the productive report and re-doing all the changes I made during development may not be an option either, depending on the amount of changes. Any tips what else to do?

[prikala]

I have not used this myself but using parameter updateTargetObjectWhenOverwrite in system.xml might help:
   http://www-01.ibm.com/support/docview.wss?uid=swg21625148

Also see https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.ug_cra.10.2.2.doc/t_asg_changethebehaviorwhenyoucopyobjects.html
I am not sure what is meant by
   Tip: Do not change the default behavior if the objects you are copying are reports that reference packages.
Somehow that makes me suspicious. Does this parameter have side effects I don't understand...

[hespora]

I'm not sure about that phrasing either. Also, in the technote you linked, there's another link, saying

A COPIED REPORT IS NOT LINKED TO THE PACKAGE OF THE DESTINATION REPORT

:-\