Hi everyone, in our App we are often required to show 200-300 objects in a table or gallery (kanban board for example) and have advanced filters options that go beyond just simple text searches in a column (e.g. searching for an attribute in an associated object). In order to make that possible we use an OQL query as a string, that gets updated depending on the set filters by the user. When redirecting from that page (by clicking on a row or an object of the result) the page is increasingly slow, due to many non-persistent objects loaded in the cache/runtime. This has to do with the retrieval via the OQL. The redirection and overall performance of those tables/views have gotten so slow, that we have to do somthing about it. Anyone with a similar problem or different approach how to handle those types of overview pages with advanced filtering? Any suggestion is appreciated! BR Markus
↧