Get the sys_id of a record inserted with…

Server-sidebeginnerTested on Xanadu

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

Capture the sys_id of a newly created record after insertion

Business Rule

(function executeRule(current, previous) {
    var incident = new GlideRecord('incident');
    incident.initialize();
    incident.short_description = 'Security incident for ' + current.user_name;
    incident.category = 'security';
    incident.state = 1; // New
    incident.caller_id = current.sys_id;
    incident.assigned_to = gs.getProperty('security.incident.default_assignee');
    
    var incidentSysId = incident.insert();
    
    // Only proceed if insert succeeded
    if (incidentSysId) {
        // Create related task using the sys_id we just captured
        var task = new GlideRecord('sc_task');
        task.initialize();
        task.short_description = 'Review access for security incident';
        task.parent = incidentSysId;
        task.assignment_group = gs.getProperty('security.review.group');
        task.state = 1; // Open
        
        var taskSysId = task.insert();
        
        // Add work notes to the original incident referencing the task
        if (taskSysId) {
            incident.get(incidentSysId);
            incident.work_notes = 'Review task created: ' + taskSysId;
            incident.update();
        }
        
        gs.info('Created security incident ' + incidentSysId + ' with task ' + taskSysId);
    } else {
        gs.error('Failed to create security incident for user ' + current.user_name);
    }
})(current, previous);

The insert() method returns the sys_id of the newly created record as a string — but only if the insert succeeds. Most developers miss the critical failure case: if the insert fails due to ACLs, required field validation, or business rule exceptions, insert() returns null or an empty string. This pattern is essential when you need to create related records in the same script execution — using the returned sys_id eliminates the need for additional queries to find the record you just created.

When to use this

Creating parent-child relationships in the same script (incidents with tasks, requests with catalog items)
Building audit trails or related records that reference the primary record's sys_id
Logging or notification scripts that need to reference the specific record created
Integration scripts that need to store the ServiceNow sys_id in an external system

When NOT to use this

Don't use this in client-side scripts — GlideRecord.insert() doesn't return the sys_id on the client
Don't use this for bulk record creation — use insertMultiple() or batch REST API calls instead
Don't assume the insert succeeded — always check if the returned value is truthy before using it
Don't call insert() inside a loop over another GlideRecord — you'll create N+1 database operations

Key behaviors and gotchas

The returned sys_id is a 32-character string, not a GlideRecord object — use it directly in reference fields
Business rules on the target table will fire during insert() — if they throw exceptions, insert() returns null
ACL failures will cause insert() to return null — the record is not created and no error is thrown
Required field validation happens during insert() — missing mandatory fields will cause the insert to fail silently
The sys_id is generated before business rules fire — you can access it in 'before' business rules via current.sys_id
Domain separation applies — you can only insert records into domains you have access to

⚠️

Never assume insert() succeeded. A null return value means the record wasn't created, but your script continues running. Always check the return value before using it to avoid creating orphaned related records or broken references.

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.

Alternative Approaches

Using setValue with sys_id before insert

var incident = new GlideRecord('incident');
incident.initialize();
var customSysId = gs.generateGUID();
incident.setValue('sys_id', customSysId);
incident.short_description = 'Custom sys_id incident';
incident.state = 1;

if (incident.insert()) {
    gs.info('Created incident with custom sys_id: ' + customSysId);
    // Use customSysId for related records
} else {
    gs.error('Failed to create incident with custom sys_id');
}

Use this when you need to control the exact sys_id value, typically for data migration or integration scenarios.

Trade-offs: More complex and bypasses ServiceNow's built-in sys_id generation — only use when you specifically need deterministic sys_id values.

API Methods Used

GlideRecord.initialize()GlideRecord.update()GlideRecord.get()

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

Get the sys_id of a record inserted with GlideRecord