Currently, Mendix pages only accept single objects as parameters.
We cannot pass lists directly to a page, even though microflows and nanoflows can work with lists easily.
Because of this limitation, developers must use workarounds such as:
Creating non-persistable helper objects
Storing lists via associations
Re-retrieving the same data on the page
Creating additional microflows just to return a list
This adds unnecessary complexity and affects performance.
Why this feature is needed
Allowing pages to accept a list parameter would provide several benefits:
1. Cleaner and simpler architecture
No more helper entities, associations, or extra microflows just to display a list.
2. Better performance
The list is already available in memory, no need to recreate NPEs or retrieve the data again on page.
3. Reduced server and database load
Eliminates duplicate retrieves and association updates, lowering workload on the runtime and DB.
Enabling list parameters for pages would simplify UI logic, reduce boilerplate, improve performance, and make Mendix apps easier to build and maintain. This would be a valuable addition to the Mendix platform.