Pega 8.6.1 upgrade issue

User Experience
, , ,
1

I am unable to sort the table post upgrade of pega 7.1 to 8.6.1.

2

@Nandhini.Mani please could you provide the following details:

  • can you provide details of the table data source?

  • can you provide screenshots illustrating the working and non-working behaviour?

I have found one example which is currently being looked at by our engineers. In another user scenario the sort order of CaseIDs in a Grid has changed following a patch update above 8.4.4.

Originally in earlier releases the Case ID (pyID) appears to be sorted numerically based on the number after the case prefix. e.g.
T-1
T-2
T-10
T-11

After patch update to 8.4.4 the order is alphabetically e.g.
T-1
T-10
T-11
T-2

The reason for the change in behavior seems to be the fix in 8.4.x onwards in the activity pzSortClipBoardData code using myComparator[0] = “”;

vs
myComparator[0] = “Lib(Pega-RULES:Sort).compareUnicode”;

===> Is this the issue you are also encountering?

This issue has been found to be a product issue and logged under BUG-656552. (Sorting is not working properly in Grid/Table).

It is due to be fixed in 8.6.4 which is due out : April 22nd

If this is not your issue, please can you provide more details?

3

@MarijeSchillern :

Data source: Datapage

In table we have sorting present for createdatetime, when we click on sort

  1. Ascending order is working fine (MM-DD-YYYY)

03/01/2022 09:55 AM

04/04/2022 05:21 AM

04/04/2022 05:22 AM

04/05/2022 09:33 AM

04/06/2022 05:09 PM

04/06/2022 05:11 PM

  1. Descending order is not working (MM-DD-YYY)

04/06/2022 05:09 PM

04/05/2022 09:33 AM

04/06/2022 05:11 PM

04/04/2022 05:21 AM

04/04/2022 05:22 AM

03/01/2022 09:55 AM

4

@Nandhini.Mani if no other forum users provide any input I would suggest that you log that as a support incident.

If you go down that route, please can you provide the incident number here in the post so that we can help track it?

5

@MarijeSchillern Thank you.

We created the INC for this.

6

@Nandhini.Mani Could you please provide the incident number here in the post so that we can help track it?

7

@MarijeSchillern Please find the INC-219859

8

@MarijeSchillern is this issue resolved ?I mean pyID sorting issue.

9

@Nandhini.Mani INC-219859 is not related to this issue, nor from the same company. Can you please check again which support ticket you have logged for this?

10

@MarijeSchillern It was an issue related to dynamic layout refresh action on focus event.

Issue got resolved.