Statistics
The Highest Post

Total Post till Wednesday, November 20, 2024 : Peter Agyekum:

Total Post till Wednesday, November 20, 2024 : James Say:


Total Post till Wednesday, November 20, 2024 : Peter Agyekum:


Total Post till Wednesday, November 20, 2024 : Mercy Soya:


Total Post till Wednesday, November 20, 2024 : Jay Man:


Total Post till Wednesday, November 20, 2024 : Jonathan JeBrown:


Total Post till Wednesday, November 20, 2024 : Samson Koa:



Total Participant for Reply Posting Wednesday, November 20, 2024 : 94

Statistics
Count 94
Avg 21.00
Min 21
Max 21
Angualr Top questions

Details


 Consider your use cases How much data do your users truly need to review on a single screen? If you identify that your list transactions are slow, find out how much data your users are requesting. When a user selects Show 100 rows per page on a list, this sets a user preference. From that point forward, every list I the platform will show that user 100 rows. This includes related and embedded lists on forms as well as the list views where the user sets the preference. If you have a sufficient number of users who are requesting high numbers of rows, you could experience a platform-wide performance degradation because those row counts are making such high demands on the memory required from the JVM to render the lists. This becomes problematic when a table with many reference fields has to render a list. The the platform has to build relationships for all of the reference fields for all the rows displayed on screen. For most service environments, agents can’t practically use more than 20–30 rows at a time. If the page load is fast, you can make a good case for “paging” to the next chunk of results rather than scrolling down. Consider using the ‘Glide.UI.per_page’ property to define the items per page drop down option visible for users.
Related Topics