Related Lists
Discover all related lists for the current record, see record counts, and find hidden relationships that aren't on the form.
Last updated: March 22, 2026
Last updated: March 22, 2026
The Related Lists tool scans all reference relationships for the current record's table hierarchy and shows you exactly which related lists have data, which ones are on the form, and which ones are hidden. It's the fastest way to discover relationships you didn't know existed.
Open it with /skrl or /skrelatedlists, or select Related Lists from the Sidekick menu. The tool requires a form to be open — it reads the table and record from g_form.
When you open the tool, it:
incident → task → cmdb) to find all parent tablessys_dictionary for all reference fields pointing to any table in the hierarchyResults are organized into three collapsible sections:
The most actionable section. These are related lists that have matching records for the current record but are not displayed on the form. This helps you discover data relationships you might be missing.
Each item shows the table label, technical name (e.g., task_ci.task), record count, and a link icon to open that related list in a new tab.
Related lists currently displayed on the form, ordered to match their visual position on the page. Each item shows:
Related lists with zero matching records that aren't on the form. This section is collapsed by default to keep the view clean.
Use the search box at the top to filter related lists by table label or technical name. The filter applies across all three sections in real-time.
The tool automatically excludes tables that typically produce noise:
var__ (variable tables)ecc_ (ECC queue tables)00 (internal/system tables)Scripted related lists (prefixed with REL:) can appear on the form but cannot have their record counts queried through standard APIs. These are noted in the summary with the message: "Scripted relations are not in this list."
Counts are fetched using GraphQL _rowCount queries in batches of 40 for performance. If GraphQL is unavailable or returns an error for specific tables (e.g., due to ACL restrictions), the tool automatically falls back to the REST Stats API for those tables. Items where neither method succeeds show ? as the count.