Users with large lists created from large tables can use the glide.ui.fetch.list.record.count.asynchronously property to continue interacting with their list, while the total record count loads.

Before you begin

Role required: admin

Procedure

  1. Navigate to All > System Properties > All Properties.
  2. Select New.
  3. On the form, fill in the fields.
    Table 1. System Property form
    FieldDescription
    Name The name of your system property as glide.ui.fetch.list.record.count.asynchronously.
    Description Type a brief, descriptive phrase describing the function of the property.
    Choices Comma-separated values for a choice list. If you need a different choice list label and value, use an equal sign (=) to separate the label from the value. For example, Blue=0000FF, Red=FF0000, Green=00FF00 displays Blue, Red, and Green in the list, and saves the corresponding hex value in the property value field.
    Type true I false
    Value Set the desired value for property.
    • True to enable this feature.
    • False to disable this feature.
    Ignore cache

    The system stores system property values in server-side caches to avoid querying the database for configuration settings. When you change a system property value, the system always flushes the cache for the sys_properties table. Use this field to determine whether to flush this property's value from all other server-side caches.

    The default value of false causes the system to not ignore flushing caches, which results in flushing all server-side caches and retrieving the current property value from the database. Set this field to false when you want to ensure all caches have the current property value. The true value causes the system to ignore flushing some server-side caches, which results in only flushing the cache for the sys_properties table and preserving the prior property value in all other caches. Set this field to true to avoid the performance cost of flushing all caches and retrieving new property values. Typically, you should only set this field to true when you have a system property that changes more frequently than once a month, and the property value is only stored in sys_properties table.
    Private Set this property to true to exclude this property from being imported via update sets. Keeping system properties private prevents settings in one instance from overwriting values in another instance. For example, you may not want a system property in a development instance to use the same value as a production instance.
    Read roles Define the roles that have read access to this property.
    Write roles Define the roles that have write access to this property.
    Application The scope of the feature is enabled Global by default.
  4. Select Update.
    The property is now active and the list loads asynchronously.