Skip to main content

Performance troubleshooting: Listings are not loading

Error when loading specific field lists: Error reading data: undefined

H
Written by Harry Ledger
Updated over 2 months ago

In areas of the system where a list of records is displayed, a field list is used to determine which fields appear. This list can include fields from tables or views related to the main record type.

Fields in the list can be set to always show or always be hidden. Hidden fields still retrieve data in the background, just like visible ones.

If you consistently encounter error messages or unusually slow load times when accessing a list, it’s likely that a field in the field list is causing the issue.

Errors you may see

  • Error reading data: undefined.

  • Execution timeout expired.


Configuration checks

These checks are for users with advanced experience with the SelectHR system.

Check

Additional information

Is the field list adhering to standard configuration?

Where best practice has been followed, compare the field list on the slow/erroring process to a standard field list on the HR (v2.0) menu set.

If the standard listing loads, this signifies that the error list has been configured.

Does the field list pull from more than one data source?

Where a field list has more than one data source, one of those data sources may be slow loading or not intended for field list use. Data sources with the name Extra Detail included are known to be problematic and should be avoided where possible.

If only one field is included in the field list, does the listing load quickly?

  1. Copy the field list where the problem is observed, remove all fields from the field list with the exception of one from the source table (e.g. Person Number/First Name/Surname), and apply this to a copy of the process.

  2. If the field list loads successfully and in a timely manner, this confirms that the issue is with one of the fields on the field list.

  3. At this point, add each previously included field back to the field list one by one, until the issue can be replicated again.

  4. Once the issue is present again, the last field you added is the one causing the issue and should be considered for removal from the field list.

If an alternative data source for the field is available from the same source table, it is recommended to use this instead.

Did this answer your question?