Use the Same iDOCID to Access Reports

[Former Member]

Hi,

We have users using opendocument to access reports utilizing iDOCID= parameter.  The problem we have is that a report is replaced with a copied report after it has been edited, the iDOCID changes and therefore all links are broken until the user changes the link. 

This is due to the fact we do not let users edit reports in our Public area so the only way to edit a report and keep the iDOCID the same is to "move" it from Public to Favorites and "move" it back to Public.  This isn't acceptable because the report is not available for the amount of time it is not in the Public folder which may be days.  Since our environment is like this, users only have the ability to make changes to a copy and replace the Public report with the copied report, changing the iDOCID for the opendocument links.

I'm looking for a solution where the iDOCID stays the same and was wondering if anyone had a solution to this problem.

We are running BO v3.1.

Thanks for your time,

Dave

[Former Member · Accepted solution]

Hi David,

Best practice is to use

http://<servername>:<port>/OpenDocument/opendoc/openDocument.jsp?iDocID=Aa6GrrM79cRAmaOSMGoadKI&sIDT...

CUID will not change when u transport from dev to Q or Prod.

Thanks,

Raj

[CarlyThomas]

Is it possible to use the doc name (I think the param is called sDocName) instead of the DocID in your opendoc URL?

Or do you have multiple reports with the same name?

I can't think of another way because an overwrite isn't allowed and a copy will always create a new ID because the original still exists when the copy is created.

I hope that helps,

Carly

[Former Member]

Hi Carly,

Thanks for the response. DocName can't be used because users may have a copy of the report with the same name in their folder like you mentioned (I can't control if people don't rename the document) and the report that gets opened might be the local or the public copy.

I am hoping there is some solution through the SDK or some other custom solution someone has run across.

Thanks!

Dave

[former_member188911]

The best practice is to have a DEV system where you edit the documents and then promote them to PROD with LCM the benefits would be:

- higher consistency  

- version handling

- safer promotion of content

- you keep the metadata specification 

see http://help.sap.com/businessobject/product_guides/boexir31SP4/en/xi31_sp4_lcm_user_en.pdf for more information