[MGNLUI-8654] Sorting doesn't work in list view for a high amount of items Created: 15/Jan/24  Updated: 16/Jan/24

Status: Open
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.41
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2024-01-15 at 13.54.38.png     XML File scripts.duplicatePage.xml    
Issue Links:
Relates
relates to MGNLDAM-1368 Sorting alphabetically doesn't work c... Selected
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Team: AuthorX

 Description   

Steps to reproduce (in demoauthor)

  1.  Execute the attached script so the amount of pages increases substantially
  2.  Open pages-app and go to the list view
  3. Sort by template for example

Expected results

Pages are ordered correctly by template

Actual results

Order is not correct

Workaround

Development notes



 Comments   
Comment by Roman Kovařík [ 15/Jan/24 ]

There is a disparity between the content visible in the UI and the data stored in the database for some columns. For instance in the page template column, the item labeled 'Travel Home' is stored as 'travel-demo:pages/home' in the backend. The backend, lacking awareness of the UI rendering, employs 'travel-demo:pages/home' for sorting purposes.

Although the UI framework attempts to address this possible issue by post-sorting based on the rendered value, it can only sort the items within the viewport. While this approach may suffice for certain scenarios, it doesn't work for applications with a huge number of items.

Attempting to render all backend items just for the purpose of sorting is of course not possible because obvious performance implications. Disabling sorting for columns affected by this issue is a possible solution, but it also disables sorting functionality for cases where it functions as intended.

Generated at Mon Feb 12 09:57:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.