Use getRefRecord to access a reference field record

The getRefRecord() method retrieves the complete GlideRecord for a reference field using the query ServiceNow already executed when loading the parent record. Dot-walking like current.assignment_group.name triggers individual field lookups for each property access, but getRefRecord() gives you the full record object once. The critical difference: getRefRecord() returns null for invalid references, while dot-walking returns empty strings that can mask data integrity issues.

When to use this

• When you need multiple fields from the same reference record in a single script
• When you need to validate the reference exists before proceeding with business logic
• When you need to call methods like canRead() or isValidRecord() on the referenced record
• When building complex conditions based on reference record properties in Business Rules or Script Includes

When NOT to use this

• Don't use for single field access — current.assignment_group.name is more efficient for one field
• Don't use in client-side scripts — reference fields don't populate the same way on the client
• Don't use when looping over a GlideRecord that contains the reference data you need — query with addJoinQuery() instead
• Don't use for display values only — getDisplayValue() on the reference field is lighter weight

Key behaviors and gotchas

• Returns null if the reference field is empty or points to a non-existent record — always null check
• ACL restrictions apply to the returned GlideRecord — fields may be empty if the user lacks read access
• The returned GlideRecord is read-only by default — call setWorkflow(false) before update() if modifying
• Performance degrades in loops — if processing many records with the same reference, cache the getRefRecord() result in a map
• Domain separation applies — you may get null for cross-domain references the current user cannot access
• Works with reference fields only — will fail on string fields that contain sys_ids