I am working with a client who has Business Objects installed. Reports are developed in Crystal and saved into a development folder. Then the rpt is moved to a production folder and brought into BOE via CMC by the BOE administrator. Then it is scheduled for delivery.
In some cases there are over 50 scheduled instances of a report.
In my experience it is complicated when you have to make a change to a report that has been published and scheduled in a way that will maintain the existing scheduled instances. I have always done this by opening the report in Enterprise, making my changes and then saving it back to Enterprise (I am talking about an environment where there is no TEST BOE environment so we cannot use the import wizard/ update / merge functions).
However, my client believes that they can just make the changes to the report in the development folder, copy the rpt object to the production folder and expect the schedules to remain intact. This has not been working because, as I tried to explain, they are destroying the CUID binding.

We now have a situation where a report needed to have a parameter added to it. It has over 100 scheduled instances (they don't want to use bursting for some reason). They don't want to have to reschedule 100 instances.

Could someone in the know please outline the proper technique for maintaining scheduled reports so that the published instance only needs to be refreshed and the individual instances rescheduled by just using the replace option and adding the new parameter value? Is this even possible?

Finally, what happens if the reports that were published were in folder A and then are moved to folder B? Is the binding broken for these if the report needs to be maintained?

Thanks in advance for all of your expertise.