Not being familiar with your domain model this might or might not be an option for you.
In some case we prevent the association calls by creating some display attributes for values that otherwise need to be retrieved over association. This will help in the performance of the grid/ listview. It does however increase the complexity of your domain model and adds redundancy and the need for data updates. Depending on your situation this might be a possible route. Another might be redesigning your model for this purpose, but without further information on the model I can not provide any answer here.
Upto Mendix version 7.something (7.8 I believe) the reference selector for non-editable attributes did retrieve its list of values. These values are never used since the attribute is non-editable. So if you are still on a low 7 version, upgrade will improve the performance for your page by the amount of time that it currently takes to do the retrieve of the reference selectors.
Thanks for your quick answer Erwin,
Most of the associations are going from one Entity to different other Entities and offer Reference Selectors. There is also another ListView inside the ListView on that page (also read only).
To properly understand your approach: For the main entity (from which the associations originate on that page), you would add additional attributes that store all the ReadOnly data I currently collect via the Associations fetch? Would you create these attributes within the main entity or create 1 new entity over 1 association for it?
And when would you populate these new “display attributes”? When opening the page via a microflow? Do I need to “commit” them or do you think it would be enough to just leave them in memory?
Thanks a lot for sharing possible solutions.