In a Section table Rule for the optimization Code, when we have two different Similar optimized Sections in two different harnesses. After opting for personalized view in any one section then in another section we can’t able to column default sorting. But, onclick of three dots by clicking on “click to sort in Ascending/Descending” funtionality is working
This is not an issue. This is happening with the enablement of that setting. Have noticed this at my end also.
In optimized table sections, when two similar sections are used in different harnesses and personalized view is enabled in one, Pega saves user-specific settings like column order and sorting. Because of this, the default sorting in the second section won’t work as expected, since the saved view takes priority. However, when you click on the three-dot menu and choose “Sort Ascending” or “Sort Descending,” it works because it applies sorting directly on the UI. To fix this issue, try giving a unique table ID to each table so that personalized settings don’t overlap, or clear the personalized view to reset the default sorting
Could you please confirm where can we provide this Unique table ID, Is it something we can update at the UI level or at the DB level.