Dan Martinez
Tera Expert

Overview

While we all wait for RaptorDB to be released on all instances, it is always great to remember there is a feature that allows us to speed up the form loading on any record. Users can change their preferences to speed up how forms load but we can also configure the instance to do so for all of them as the default option. However, depending on the scenario this may not be the best option. We will go through the three options we have and when each is better.

 

Changing the user preferences

If we go to our picture on the top right corner found in the backend and click on "Preferences" we will see the dropdown for "Load related lists in classic forms" under the "Display" section.

 

art.jpg

 

This will show three options:

  • With the form: This is the defaulted selection. It means related lists will be loaded along with the form, so if the form took 0.2 seconds in loading but the related lists took 1 second, you would see everything at once after 1.2 seconds
  • After the form loads: In the example mentioned above, you would see the form in 0.2 seconds and you would see the related lists loading for 1 second.
  • On demand: Related lists are not loaded unless you request it by clicking on the button appearing on them

The option you choose has to match the way you use the platform. For instance, selecting "On demand" can be problematic if you tend to use the related lists most of the times. "With the form" can cause unnecessary delays if you use them from time to time. "After the form loads" could be described as the sweet spot, since forms will always be loaded as fast as possible, but you will also have the related lists loaded in any case.

 

In the example before there may not be much difference, but bear in mind, in unoptimised instances, related lists can take several seconds to be loaded, slowing you down without any reason.

 

Bear in mind, as mentioned on the dropdown this only works on the backend and does not apply to UI Builder-based User Experiences (workspaces).

 

Admin perspective

These changes are stored in the "sys_user_preference" table, so they can be changed by admins. The user preference is "glide.ui.related_list_timing" and options are "default" (with the form), "deferred" (after form loads) and "ondemand" (On demand) as mentioned in the official documentation.

 

If this post was useful to you, please like it  👍 and share 🌍