Consider a scenario where we have two entities: Books and Chapters, with a one-to-many relationship (i.e., each book can have multiple chapters). I currently have a read-only grid that displays records based on the Book entity. One of the columns in this grid is called "Chapters", which displays all associated chapters in a bulleted list.
Since a book can have more than 10 chapters, I'm currently fetching all chapters into a local variable and indexing them based on the Book ID to display in the corresponding grid row.
This approach works fine for now. However, I'm concerned about performance if the chapter count increases more than 5000
Does anyone have suggestions on how to handle this scenario more efficiently?
Discussion posts and replies are publicly visible
I think the purpose is the more important question. As a user of this application why would I navigate to this list? What do I want to achieve?
Hi Stefan Helzle . This is just a similar scenario I mentioned earlier. In my actual use case, the user will add multiple child records (possibly more than 10) while creating a new case. On the dashboard, we display a case grid, and the requirement is to show one of the related child records in a column of the case grid, along with an icon beside it to expand and view the full list of related records.
So, it is about these child record, right? Did you consider to load them on demand? You could add a local variable to the individual cell, and load the data for this cell only when the user clicks the icon.
Yeah. That works. I think i would do query in cell level if count of child record data is 10 so that i dont need to query for all cells which is having less child records. Thanks Stefan Helzle