We have separate Development, Staging and Production Cognos environments for developing, testing and promoting framework updates and other large scale changes. However, for simple report modifications we have "Report Development" and "Report Staging" folders in the Production environment where can copy existing reports, modify, test and then promote to the "Report Production" folder that is visible to standard users. Many of our users have Report Views in their My Folders which point to production reports. When we copy a report (or report folder containing the main report and drilldowns) from "Report Staging" and paste/overwrite to "Report Production", the user's Report View links break, and they have to reselect the Source Report in the Report View properties even though the new report has the same name and is in the same location. Shortcut links do not break.
Is there anyway we can replace a report in the production folder with an updated version from the staging folder without breaking the Report View links?
I ran into this issue last year and found that following the instructions on this page did the trick.
http://www-01.ibm.com/support/docview.wss?uid=swg21625148
A restart of your Cognos services will need to be done after implementing this to allow it to work.
That looks perfect Karti, thanks. I will implement and see if it helps.
Hi,
I ran into the same issue after upgrading to Cognos 10.2 and changing the parameter "solves" this issue certainly.
Do you have any idea what was the reason to change this behavior with the release of 10.2? We have technically based our processes on this feature to overwrite objects. I'm just trying to reproduce what IBM was thinking by introducing this feature..... :o
Thanks and best regards,
Timm
I'm not sure what their thought process was when they implemented this. I'm just glad that they decided to put in this "fix" to revert back to the old way, without having to wait awhile before it came out with a fix pack.
Also, when applying a fix pack to your environment, this systems.xml file will be reverted to its old copy (or new depending on if that fix pack has a new version of the file) so you will have to re-apply this fix.