GlideRecord.get() — ServiceNow API

get(sys_id)→ boolean

beginnerTested on Xanadu

What It Does

The get() method performs a direct record lookup using the primary key (sys_id). When you call this method, ServiceNow bypasses the query engine and goes straight to the database with a SELECT statement targeting the specific record. This makes it significantly faster than constructing a query with addQuery() and query() for single-record retrieval.

Internally, the method validates the sys_id format, executes the database lookup, and populates the GlideRecord object with field values if the record exists. The GlideRecord becomes positioned on the found record, meaning all field accessors (getValue(), getDisplayValue(), dot-notation) immediately work without needing to call next().

The method returns true when a record with the specified sys_id exists and is accessible under current ACL restrictions. It returns false when no record exists, when ACLs deny access, or when the sys_id is empty. The GlideRecord object remains valid but empty when false is returned.

Edge cases include malformed sys_ids (returns false), sys_ids from different tables (returns false), and records that exist but are filtered out by read ACLs (also returns false). You cannot distinguish between these scenarios from the return value alone.

Unlike query() which returns a result set, get() positions the GlideRecord directly on the target record. This means calling next() after a successful get() will return false and move past the record.

When to Use This

Use get() when you have a sys_id and need to retrieve exactly one record. This includes scenarios like following reference field values, processing records from arrays or lists of sys_ids, and lookup operations in Business Rules where you have the current record's sys_id. The method is particularly effective for checking record existence or retrieving parent records via reference fields.

Avoid get() when you need to query by other fields—use addQuery() and query() instead. Never use get() in loops where you're checking existence for many records—batch the lookups with addQuery('sys_id', 'IN', arrayOfIds) for better performance.

Common misuse includes attempting to use get() with field values other than sys_id, calling it repeatedly in loops without caching results, or using it when you actually need multiple records. These patterns indicate you should restructure your approach around proper queries or GlideAggregate for counting operations.

Return Value

Returns a boolean value: true when the record exists and is accessible, false otherwise. The return value is a genuine JavaScript boolean, not a string or number, making it safe to use directly in conditional statements. When true, the GlideRecord object contains all field data and is immediately usable.

When the method returns false, accessing field values will return empty strings or default values rather than throwing errors. Always check the return value before proceeding with field operations to avoid logic errors based on empty data. The GlideRecord remains in a valid state even after failed get() calls and can be reused for subsequent operations.

Free Newsletter

Enjoying this? Get one deep-dive per week.

Join 1,000+ ServiceNow pros — scripts, GlideRecord patterns, Flow Designer techniques, and career moves. Free.

Platform Behavior & Side Effects

Read ACLs are enforced—records blocked by ACLs return false as if they don't exist
Business Rules do not execute during get() operations since no data modification occurs
Database performance is optimal—single SELECT by primary key with automatic indexing
No database writes occur, so audit fields (sys_updated_on, etc.) remain unchanged
Query caching does not apply since this bypasses the query engine entirely
Works identically across all server-side contexts (Business Rules, Script Includes, Scheduled Jobs)
Memory usage is minimal since only one record's data is loaded into the GlideRecord object

Parameters

Name	Type	Required	Description
sys_id	string	Yes	The 32-character sys_id of the record to retrieve. Accepts empty strings (returns false) but throws errors for null or undefined values. Leading/trailing whitespace is automatically trimmed.

Chrome Extension

Sourdough: ServiceNow Monitoring and Analytics

A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.

Instance HealthGraphs & ChartsAPI HealthDeveloper ToolsQuick SearchInstance Switcher

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview

Tasks

CMDB

API

Metrics

Monitor

Internals

Instance:sourdoughdev·Version:Yokohama

Instance StateONLINE

System StatusFully Operational

Session Timeout90 minutes

Logged-In Sessions2 (20 active)

Build Nameyokohama-12-18-2024_p1

IP Address10.159.128.43

Instance HealthHealth Score: 90%

🔥 5dSourdough (Chrome Plugin)Dark Mode

Code Examples

Basic usage — retrieving an incident by sys_idbasic

// Check if a specific incident exists and get its details
var incidentId = 'a9b8c7d6e5f4g3h2i1j0k9l8m7n6o5p4';
var incident = new GlideRecord('incident');

if (incident.get(incidentId)) {
    // Record found - safe to access fields
    gs.info('Incident ' + incident.number + ' has priority ' + incident.priority);
    gs.info('Description: ' + incident.short_description);
    gs.info('Assigned to: ' + incident.assigned_to.getDisplayValue());
} else {
    // Record not found or access denied
    gs.warn('Incident with sys_id ' + incidentId + ' not found or inaccessible');
}

// GlideRecord is still valid for reuse
var anotherId = 'b0c9d8e7f6g5h4i3j2k1l0m9n8o7p6q5';
if (incident.get(anotherId)) {
    gs.info('Found another incident: ' + incident.number);
}

This example shows the standard pattern: call get(), check the return value, then safely access fields. The boolean return makes it perfect for if-statements.

Intermediate — following reference fields to parent recordsintermediate

// Get catalog task and check its parent request item
var taskId = current.sys_id.toString(); // From a Business Rule context
var task = new GlideRecord('sc_task');

if (task.get(taskId)) {
    var requestItemId = task.getValue('request_item');
    
    if (requestItemId) {
        var reqItem = new GlideRecord('sc_req_item');
        if (reqItem.get(requestItemId)) {
            // Now check the parent request
            var requestId = reqItem.getValue('request');
            var request = new GlideRecord('sc_request');
            
            if (request.get(requestId)) {
                gs.info('Task belongs to request ' + request.number + 
                       ' for user ' + request.requested_for.getDisplayValue());
            }
        }
    }
}

This demonstrates chaining get() calls to traverse reference relationships. Each get() call is checked before proceeding to avoid null reference errors.

The classic mistake — using get() in loopsadvanced

// WRONG: Inefficient individual lookups
var userIds = ['id1', 'id2', 'id3', 'id4', 'id5'];
var activeUsers = [];
for (var i = 0; i < userIds.length; i++) {
    var user = new GlideRecord('sys_user');
    if (user.get(userIds[i]) && user.active == true) {
        activeUsers.push(user.name.toString());
    }
}

// RIGHT: Batch query approach
var user = new GlideRecord('sys_user');
user.addQuery('sys_id', 'IN', userIds.join(','));
user.addQuery('active', true);
user.query();
var activeUsers = [];
while (user.next()) {
    activeUsers.push(user.name.toString());
}

The wrong way makes N database calls, while the right way makes one query. Use get() for single records, but batch operations when processing multiple sys_ids.

Gotchas

Calling next() after a successful get() returns false and moves past the record, since get() positions the GlideRecord directly on the found record.

Empty string sys_ids return false silently, but null or undefined sys_ids can throw runtime errors depending on the ServiceNow version.

Records blocked by ACLs return false exactly like non-existent records—you cannot distinguish between these scenarios from the return value.

Using get() with a sys_id from a different table than the GlideRecord returns false, even if that sys_id exists in the other table.

The sys_id parameter is automatically trimmed of leading/trailing whitespace, which can mask issues with data containing extra spaces.

Test Your Knowledge

Quick 3-question quiz — see how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue