The default page filters are not showing up in dashboards when the PERSIST option is checked in the page filter.

Document ID : KB000045991
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:
This KB article explains about 2 issues and the cause for it. Both the issues share the same root cause.
In a dashboard having multiple tabs,
1. The default value set up at the portlet filter is not showing up in the dashboard
2. Even if the PERSIST option is checked, the filters does not persist across different tabs in the portlet page.

Cause:
1. Create a portlet filter with 4 attributes
    Attribute A, Attribute B, Attribute C & Attribute D
 Attribute A should have a default value as 'Apple'
 Attribute D should have a default value as 'Australia'
2. Create a portlet page with tabs and create 4 tabs under this portlet page
    Tab 1, Tab 2, Tab 3, Tab 4
3. Navigate to each of the above tabs and under Page Filters, add the portlet filter created in Step#1 and check the PERSIST check box.
4. Also, click on the Filter mappings in each of the above tabs under page filter and
   Tab 1 - map filter attribute A and B
   Tab 2 - map filter attribute A and B
   Tab 3 - map filter attribute C and D
   Tab 4 - map filter attribute C and D
5. Publish the portlet page
6. Confgure this portlet page to show in the Home Menu
7. Navigate to the portlet page
   Expected and Actual: The landing page of the portlet page is Tab 1 and the page fitler is showing correct values for Attribute A and B
8. Click on Tab 3
   Expected: The page filter should show the default value for Attribute D which is Australia
   Actual: The page filter shows the first value in the statis lookup we created for Attribute D and not Australia.

Resolution:
The root cause for the default filter value not showing up is 'PERSIST'. The system is designed in such a way that, When PERSIST option is checked, the filters
are retrieved from DB only for the landing page and then it gets cached. In the above example, Attribute A and B is configured to show in Tab 1 and they are cached.
Since Attribute c & D is not in Tab 1, they won't be cached and when navigating to other tabs which has C and D, the system would just pick the first value in the lookup.
This has been logged as BUG CLRT-80992 and is under development review.

Work Around:
Uncheck the PERSIST option and this will force the system to pick the filter value from the DB each time the tabs are swtiched.
But with this work around, the PERSIST functionality cannot be used which means if you filter for something in the first tab, it will not persist when moving to other tabs in the portlet page.