BI Publisher - All reports gets error after renaming custom folder

Mohammed Kaja Nawaz L J

Summary

How to resolve reports getting error after renaming custom folder where report resides.

Content

After renaming the folder where report resides. It gives below error:

oracle.xdo.servlet.CreateException: oracle.xdo.servlet.CreateException: oracle.xdo.servlet.CreateException: oracle.xdo.servlet.CreateException: Data Model definition not found:

WorkAround : I found workaround by clicking on Edit report and then view report which resolves but problem is we have many reports under custom folder which got renamed. What is the ideal solution to resolve it?

Version

11.1.1.9.0

Skolli-Oracle

Its not recommended to rename the custom folder.
This is due to the fact that the "Customize" feature refers to the exact seeded folder structure under custom folder.
As per my knowledge, the only work-around is to edit the report individually.

Mohammed Kaja Nawaz L J

Custom doesn't mean seeded "Custom" folder present, I created new folder under "Custom" directory and created all report under new folder which I created. Later I renamed the new folder which I created and it caused the above error.

Isn't something where we can restart BI publisher or cache clear to point out to new folder?

Skolli-Oracle

Currently, its not possible to change all at once.
Please log idea in idea labs:

    Idea Labs Guidelines : https://cloudcustomerconnect.oracle.com/pages/35fcc3b659

Senthilrajan V

Hi

I have seen this error while renaming the folder name or while migrating reports to a different path in another environment.

I think we get this error because the report is pointing to the old data model path, opening the report and pointing it to right data model path resolves the issue. I don't see any workaround available for this now.

-Senthil

Mohammed Kaja Nawaz L J

sure.

Sandeep S. Chauhan-Oracle

Hi, As mentioned above by Sudhir, this is not recommended to rename the folder name or objects name (datamodel, sub template, etc.) and its stated in oracle documentation as well.

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/understand-impact-taking-actions.html#GUID-7F7DFE1A-6FAC-419D-86B4-9DB40852F5C5

If moving a resource object is unavoidable, then one must edit each report that references the object to refer to the object in its new location. this is the only workaround or solution. 

Hope this helps you to close this thread.

Thanks!

Mohammed Kaja Nawaz L J

Thanks for pointing out to right information. It would be great see if solution should allow to rename without any hurdles or renaming function should be excluded in future.