Promote ui knowledge from community to Microsoft layer (#51)

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Jesper Schulz-Wedde 2026-07-01 10:41:24 +02:00 committed by GitHub
parent 292bdabe27
commit 6281e7e39a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 0 additions and 0 deletions

View file

@ -0,0 +1,23 @@
---
bc-version: [all]
domain: ui
keywords: [historical-table, list-page, descending-sort, log-entry, ledger-entry, archive]
technologies: [al]
countries: [w1]
application-area: [all]
---
# Default descending sort on historical pages
## Description
Historical list pages should default to showing the newest records first. On pages such as log entries, ledger entries, archives, and other history lists, an oldest-first default order does not align with the primary use of the page, which is typically to review recent activity.
## Best Practice
Set descending sort as the default on list pages whose primary purpose is to present historical records. This is the expected default for entry, log, archive, and posted-history pages unless there is a specific requirement to begin with the oldest record.
See sample: `default-descending-sort-on-historical-pages.good.al`.
## Anti Pattern
Using an oldest-first default order on a historical list page where users are primarily interested in recent activity. Typical signs include history, log, or entry pages that regularly need to be re-sorted to descending during normal use.
See sample: `default-descending-sort-on-historical-pages.bad.al`.