Report View Link to Report

[globalbear]

I have a report that is target of several hundred report views in different users My Folders.

Now, I have made some changes to the report and then deployed the changed report to our production environment. In doing this I get a new CAMID in Content Store for the new/upgraded report. The original report still exists in the portal and the report views point to the old one.

Now - I want to change to which report the report views point. You could go into each and every report view manually to do this but that would mean loosing all parameter values besides the fact that there are hundreds of views. That is no good option.

Is it possible to bulk update source report link for report views somehow? Only way I could think of was changing the CAMID in Content store but that doesn't seem like a very good idea.

Anyone have a solution to this problem?

What I will do for now is to move the old report to a hidden folder that no user can see. This will mean that the report views will still work but that they are linked to the old report. If a user want to setup a new report view he can only see the new report and not the old one.

In effect there will be two versions of the same report in the portal - not an optimal situation.

[tupac_rd]

did you rename the report in dev, before deploying it to Prod, or did you repoint it to a different package. Coz we do what you are saying all the time that is make changes to a Prod report in Dev and redeploy it to Prod, and none of the report views linked are broken...

[IceTea]

Anyone have a solution to this problem?

Is copy&pasting the new report definition from clipboard into the old report on production system a fast and workable option for you? Then you're done for the moment.

[globalbear]

I started in development with a report called "Report A". Then a copied that report to "Report B".

In that way a have both the old report and the new, upgraded report in the development environment.

When I had made all the changes I should and was satisfied with the result I deployed Report B from development to production. Then I had two different reports in production; Report A and Report B.
All my report views point to Report A.

tupac_rd: Both reports use the same FWM package but they have different names (Report A vs Report B). The reason for having two versions was to have a point to return to if things went wrong and to have a version to compare the upgraded report with.

IceTea: Copy/Paste won't do the trick I'm afraid. The behaviour when pasting the xml into report studio is that you get a NEW report (with a new Camid). If you try to "Save As" over the old report (Report A) all your links will be gone since the report will have a new camid. Otherwise I would like the option to a) open Report A in report studio and b) open Report B from notepad and still be "inside" Report A in report Studio. In that way the camid would be the same. Report studio doesn't work that way I'm afraid (at least I haven't got it to act like that).

One option is probably to do the "save as" trick in the development environment from Report B to Report A and then deploy Report A from envrionemnt to production. The old Report A would be overwritten with the new upgraded Report A from development. Hopefully the camid would be the same and the links would still work. I haven't tried that option - we still have the old report in a hidden folder so all our old links still points to the old report version. Not optimal but good enough.

[tupac_rd]

there might be a very good reason, why you have things over complicated, or maybe I don't understand your complicated situation and I am oversimplifying things..........either way, can you back up Report A in dev to a different folder, overwrite Report A at current folder in Dev with Report B eith save as in Dev....

In Prod, bring back the original report from the hidden location, to the correct location in Prod and then move the report from dev to prod,


HTH
2pac