Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Moving page and its effect on saved customisation.

Hi,
I have two dashboards, They have pages as under.
Dashboard: D1. Pages: P1, P2.
Dashboard: D2. Page: P3.
There are a few saved customisations related to page P1. I rename that page to P4. I can see the saved customisations (cache cleared, logged out, logged in back). However, when I move page P4 to dashboard D2 (a different dashboard) my saved customisations are lost. I thought that the page remains the same, except that the dashboard has changed, the saved customisation should still be available. Would it not be the case? If not, what is the reason behind losing the saved customisations?
Could someone please explain?
OBI EE version is 11.1.1.7.0.
Thank you.
Regards,
Manoj.
Answers
-
Have you already looked at how and where customizations are stored?
If not do so. And check the XML. That will answer your question and you will learn sth new about the catalog at the same time.
0 -
Thanks for you reply Christian.
I have revisited this.
Scenario:
Dashboard: D1. Pages: P1, P2.
Dashboard: D2. Page: P3.
Created a non-shareable saved customisation on P1. This selection is saved under "/users/manoj/_selections/a_folder_name" folder. The Properties dialog box displays the object's type as "Dashboard Customizations".
Renamed P1 to P4. Logged off, logged back in. Visited page P4. The page was renamed in Catalog UI. The saved selection has disappeared. Dropped page P4.
Created P1 under D1.
Created a non-sharable saved customisation on P1.
Renamed P1 to P4 using Dashboard Properties dialog box. The saved selection is available.
Moved page P1 from dashboard D1 to dashboard D2. The saved selection is still available. Logged off , cleared the cache and then logged in again. And the saved selection is still available !!!!
I think the issue then was renaming the page using Catalog UI rather than within the dashboard's Edit mode.
Regards,
Manoj.
0 -
Now, when I move P4 from D2 to D3, the saved selections have disappeared. So, there is something that is yet being not considered.
0 -
Ok so you didn't check the XML...well half of what I said is better than none.
This is a shared saved customization:
<?xml version="1.0" encoding="utf-8"?><sawsel:dashboardSelections xmlns:sawsel="com.siebel.analytics.web/dashselections/v1" xmlns:sawst="com.siebel.analytics.web/state/v1" xmlns:sawx="com.siebel.analytics.web/expression/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="0.7"><sawst:envState xmlVersion="200811100"><sawst:container cid="d:dashboard" xsi:type="sawst:topLevelStateContainer"><sawst:container cid="p:68v4vnomh4gva76p" xsi:type="sawst:page"><sawst:container cid="s:69uk4271an4vb8p0" xsi:type="sawst:section">.....</sawsel:appliedStates></sawsel:ref></sawsel:xmlStatesReferredTo></sawsel:dashboardSelections>
If you look at this
<sawst:container cid="d:dashboard" xsi:type="sawst:topLevelStateContainer">
<sawst:container cid="p:68v4vnomh4gva76p" xsi:type="sawst:page">
And then check the dashboard+page this actually belongs to
<?xml version="1.0" encoding="utf-8"?>
<sawd:dashboardPage xmlns:sawd="com.siebel.analytics.web/dashboard/v1.1" xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlVersion="200810300" isEmpty="false" duid="68v4vnomh4gva76p" promptApplyButtonsState="hide" promptResetButtonsState="hide">
Hmm. Oh. Well what do you know. IT GOES BY ID!
0 -
Thank you Christian. I am sorry I did not inform on Friday that I had gone through the saved selection's xml files which was bit beyond my understanding. The dashboard+page XML is something new to me. Thank you.
The question was out of curiosity. I would have liked a feature that when a page is moved from one dashboard to another, the saved customisations too are changed to point to the new location (without a need to look at the XMLs). There may be some valid reason here from implementation perspective, for example, when a dashboard prompt's scope is set to dashboard.
Regards,
Manoj.
0 -
Everything in OBI - be it RPD or webcat - uses one of two ways of referencing:
a) IDs
b) fully qualified names
Dashboard construction and all webcat object referencing in object building uses b)
Saved selections use a)
0