Unable to Save report that is opened from Clipboard

[ajeeth_g]

Hi,

I am trying to overwrite a report with changes without breaking the Schedules & Event Studio Agents. I copied the report to Clipboard in Dev & I opened the existing report in Report Studio in prod & then Open report from clipboard. After this when I try to Save (not Save As) the report, it forces me to choose the report name. If i pick the existing report, It gives me a warning that the report links will be broken & treats it as "Save as" & breaks the links to my schedules & Agents. I will have to manually modify all the Events.

Can some one advise migrating the report through copying to clipboard option without breaking the schedules & Agents?
Appreciate your help.

Regards

[Lynn]

Hi,

I am trying to overwrite a report with changes without breaking the Schedules & Event Studio Agents. I copied the report to Clipboard in Dev & I opened the existing report in Report Studio in prod & then Open report from clipboard. After this when I try to Save (not Save As) the report, it forces me to choose the report name. If i pick the existing report, It gives me a warning that the report links will be broken & treats it as "Save as" & breaks the links to my schedules & Agents. I will have to manually modify all the Events.

Can some one advise migrating the report through copying to clipboard option without breaking the schedules & Agents?
Appreciate your help.

Regards

Why not do a deployment instead? When you open a report from the clipboard it is just a pile of XML code without any relationship to existing objects in the content store. In order to save it you will have to provide the report name for which a new CAMID will be created. Create a deployment archive instead.

[ajeeth_g]

Thanks Lynn. The current Dev & Prod environment are not in sync, I will have to redo me schedules & Events even if I do a deployment. Also Right now I am trying to move just 1 report without affecting its linked events, hence considering the XML route.
Is there no other work around to the get the "Open from Clipboard" option working?

[MFGF]

Thanks Lynn. The current Dev & Prod environment are not in sync, I will have to redo me schedules & Events even if I do a deployment. Also Right now I am trying to move just 1 report without affecting its linked events, hence considering the XML route.
Is there no other work around to the get the "Open from Clipboard" option working?

"Open from clipboard", as the name suggests, is opening the XML as something new. This means you can't just "save" because you don't have a current report from the content store open. You have no option but to save as a new report or overwrite an existing report, but either way you will end up with a new ID under the covers, so any links used to the original report of that name will break.

Lynn's suggestion of using a deployment is the way to go here.

MF.

[ajeeth_g]

Thank you MFGF & Lynn.

[Robl]

There is another way;

Open the original report,
Open the new report.

In the original report delete the pages and the queries.
Copy the queries from the new report to the old report.
Copy and conditional formats from  the old report to the new report.
Copy the pages from the old report to the new report.

It's a bit long winded - but does mean you can change the reports without deploying - if there's a reason you don't want to deploy.

[ajeeth_g]

Thanks Robl. This method works fine.

[Lynn]

That will preserve the original CAMID and thus not break any links, but you will also need to remember to copy variables, any custom classes or class changes. There may be things you can't copy/paste and will need to recreate. You'd need to re-test since forgetting to do something or leaving something existing in the original that should be removed could be a problem.

If there is a simple change to make then one could argue why not just make the exact same change in production that you made in development....this is not at all advisable but not really far off from this approach.

Either way, tread carefully because you are making multiple manual changes to a production report.

[ajeeth_g]

Yes Lynn, I understand the risks involved in this approach. I was in fact thinking of redoing the changes manually in the production copy. This approach saves some time in that regard.
The long term fix to this issue would be to sync up my Dev & Prod environment & deploy the changes.