Answer
Implement the ranking/TOP-N logic inside a proper IAL (a database view object) instead of trying to express it directly in the Data Source Designer's query box — build the IAL using either a subquery-with-ROWNUM approach or a ranking function, doing all the TOP-N filtering work inside that IAL itself, and then simply point the List Element's Data Source at that IAL. Since the IAL is a genuine database view, it supports the full range of SQL constructs, subqueries, ranking functions, FETCH clauses, that the Data Source Designer's own query editor doesn't directly support, giving much more flexibility for this kind of requirement.