Issue with Personalize table View
Hi Collaborators,
We have an issue with Personalised views of a table.
Table - we are bringing Work list based on user work queue
Data Page is source for the data loading in Table with Reload once per interaction selected and having one parameter to provide primary workqueue of OP ID profile.
The data which is loaded on the primary view (for everyone) works fine but the personalised view by the user soemtimes does not work.
Example: User 1 personalised the primary list by sorting and made it as separate view with a name. so now when its not the default View on load of portal then when he selectes his view from the table toolbar on top right corner. The UI seems (grid) seems correct with his selections that was made while creating the view but however on clicking any case from the list, it opens a different case. - on clicking 2nd case in the personlised view opens the 2nd case from the public/general view.
we could see the Data page refresh happening on selection of View from tool bar but we assume this is prior loading of the grid (means the sorting is not applied on the D page loading). we don't see any other options/workarounds to fix this.
Note: we have many personalised view by many users in PROD. so we need options/solution considering this.
***Edited by Moderator Marije to add Capability tags***
CoForge
US
@arjunkmb I ran into this issue about a year ago. It was caused by the fact that the data page used to populate the grid used a report definition with class joins. In the table, we referenced the joined properties as .pxPages(A).propName, and the solution was to map those values to a top level property on the data page using a data page response data transform. But in all honesty, it was a year ago with a different client, and I could be remembering it backwards. It could be that we needed to reference it as .pxPages instead of mapping it to a top level property.