Perspective Table sortOrder Property

Ignition Early Access
21

No, this bug hasn’t yet been fixed.
I have pulled every lever I can re: prioritization. If it’s an issue for you, contact support and have your rep add you to the internal ticket; that “bumps” its score relative to other tickets.

22

Hi,
I tried setting the props.data to ‘persistent’, and the sort order takes effect when the page first loads.
The sort order also retains after the props.data changes.

This solution is tested on 8.1.5.
Hope this will work for you too.

image
image448×670 39.2 KB

23

This trick worked for me, thanks @bao.nguyen

24

This did the trick for me as well. Thank you!!

25

image
image486×672 35 KB

Is there a way to prevent this sortation from happening? Table is sorted by time but at 10 the sortation gets confused.

Running 8.1.18

Thanks,
Steve

26

How is the column configured in props? It looks like it's doing alpha sorting; if you want to do proper date sorting the column must be configured to render as date.

27

image
Rendering as date

28

Hmm. What version are you on? I located a known issue which was resolved in 8.1.10.

29

8.1.18

30

Okay, I'll try to see what might be going on.

31

Thanks for looking into it for me!

32

I wasn't able to replicate in 8.1.18.

Here, even though the 10:XX times appears out of order, it is due to a date difference:
Screenshot 2022-11-08 at 11.32.03 AM

Even while applying the same format as your example I have the sorting I would expect. The following screenshot was taken after removing and then re-applying sort to prevent any sort of cached sorting).
Screenshot 2022-11-08 at 11.31.21 AM

Is there any chance the values in your example have different dates?

33

image
image236×559 20.7 KB

Looks like the date is the same and still follows the odd sorting when setting to MM/DD/YYYY HH:mm:ss format.

In case its worth noting, I'm pulling the tags from a historian in real time (60sec poll) via Tag History function and outputting as a DOCUMENT.

34

No, that shouldn't matter, but you'll probably need to contact support for this one as I was unable to immediately replicate the issue.

35

Not sure if this bug has been resolved but I experienced this same behavior. I set the binding to persistent as suggested and it seems to have resolved the issue. Thanks for the solution @bao.nguyen!

36

Thank you!

37

Seems like this bug is still around. Thanks for the solution @bao.nguyen