App ignores the "descending" order for a date/time field of a child table

[gioman]

Description
In a QGIS relation, the child records/features are set to be shown in a descending manner, using a date/time field and in QGIS Desktop this works ok

Not so much in MM App, where the order seems to be always ascending

Application (+ app version, build, operating system)
2026.3.2 Android 16

Steps to reproduce
See above

Expected results
MM App to behave as QGIS Desktop.

[Withalion]

Thanks for reporting this issue, we'll have a look