Issue  

Saved filters in the Case list table view are not retained after a page refresh. It resets to the default view and displays all data.

Symptoms and Impact

In Pega Platform™ 8.6 and later, filters configured in customized views of optimized tables within traditional section-based architecture may not persist after the view is saved and the page is refreshed.

Users may also encounter issues with column personalization, such as duplicate columns appearing in incorrect positions within the column selector or columns remaining visible after being deselected.

Steps to Reproduce   

1. Create or open an optimized table (Optimize Code = enabled, Personalize table = enabled).
2. Configure two or more columns to reference the same property with different formats:
   1. Example: Column A shows .DueDate as date/time
   2. Example: Column B shows .DueDate formatted as Time Remaining
3. At runtime, apply a filter to one of the date columns (for example, select a specific date range).
4. Navigate to Default View > Save As and save the filtered view with a custom name.
5. Return to the default page and open the newly saved filtered view.

Root Cause   

In Pega Platform versions 8.6 and later, when using optimized tables in traditional section-based architecture, sourcing two or more columns from the same property produces runtime issues in personal views. The platform fails to correctly persist filter state and manage column behavior when multiple columns reference the same underlying property, because the system cannot distinguish filter contexts per column.  This occurs with all property types.

Solution  

This is a known platform limitation.

Local Change

• Create a separate calculated property for each additional column instead of sourcing multiple columns from the same property.
• Create a new calculated property for the duplicate column (for example, if both "Due Date" and "Remaining Time" source from .pyDateTime, create a new property .RemainingTime).
• Configure the new property as a calculated field based on the original property.
• Update the table configuration to use the new distinct property for the second column.
• Apply and save the customized view with filters.
• Verify filters persist after page refresh.

References

Mapping table columns

Configuring fields in tables