Publishing Reports

[JohnEck]

I am wondering if anyone knows a way to update published reports without deleting and then republishing them. We add divisions on a regular basis in my company and I am getting tired of deleting and republishing thse reports every month. I attended the CDUGNA conference in 2002 and there was a vendor there that had a program that would take care of this but it wasn't a big deal then. I have since lost the vendor info and cannot find the software online. If anyone knows how to accomplish this in CE let me know or if you know the vendor let me know. Thanks for any help. I did not know where else to turn.

 

[bdreed35]

There is a patch on the CE8.5 CD that allows you to update CR8.5 so that you can interact with reports published to CE. Install the patch and you will be able to open reports from "Enterprise Folders", modify them, and then save them back to CE. This should save you a lot of time.

~Brian

 

[Turkbear]

Hi,
Just a note about one 'gotcha' in that method..
If you have set a default Username/password for the datasource that the report uses, editing it in this manner will 'blank out' the password and you will need to use the CMC to reset it.

 

[JohnEck]

I know which is why that method didn't really work for me. There is no advantage to that method. I did track down the software I was looking for. It is called the Enterprise update utility and is available from InfoTrain. If you modify a report in CR it will republish the report without changing any of the settings you have in CE like the database defaults or if you want to prompt for parameters. It also will search the CE db to find where you published the report in CE incase either copy gets moved. It does only work if you have entered the summary info, but I have found that it is important that you do this anyway.

Thanks for the help.

John Eck

 

[Turkbear]

Hi,
Actually the big advantage to that method is that it retains the Report ID# so no custom pages need to be recoded.
Resetting the password is a trivial task, compared to republishing the report and changing lots of csp code.


Side note:
Since I do not know your report designs,I can only wonder why adding or removing divisions would
require a change in a report -
we change office designations, divisions and the like often , but since our reports get their data from the database the 'knows' about the new names, no changes are needed to show the new stuff. Admittedly most of our reports use that data as group designators for summaries or listings; your needs certainly will vary.

 

[bdreed35]

Turk:

I do know what you mean about the resetting of the password because that has also happened to me on occasion. More often than not though, the password is retained. It would be interesting to know what causes it to lose the password sometimes. We also use paramters in all our reports, which will also occasionally get reset when I publish a new version of the report. Things like Destination and Format never get reset.

~Brian

 

[JohnEck]

The problem is the picklists. As we add divisions we need to add them to the picklists. We could develop dynamic picklists but we have been known to need to make modifications to the the report logic as reporting needs change and republishing them or saving over them is doen't quite meet our needs for ease of administration. One nice feature of this utility is it tracks where a report has been published based on the report name.