Understanding the Glide API Ecosystem

At its core, ServiceNow is built on a robust platform that allows for extensive customization. While the platform offers plenty of out-of-the-box functionality, developers often need to tweak behaviors, integrate with other systems, or build entirely new features. This is where the Glide APIs come into play.

Think of Glide APIs as your Swiss Army knife for interacting with the ServiceNow platform programmatically. Instead of writing raw SQL queries – which we generally can’t do directly in ServiceNow for security and abstraction reasons – Glide APIs provide a structured, JavaScript-friendly way to perform database operations, manipulate records, and even interact with the user interface. Each API is packed with methods designed to perform specific tasks, giving you immense flexibility.

Types of Glide APIs: A Quick Glimpse

The Glide API landscape is vast, broadly categorized into Client-Side and Server-Side APIs, reflecting where your script executes:

• Client-Side APIs: These run in the user’s browser, typically affecting the UI or user experience. Examples include GlideForm (for manipulating forms), GlideUser (for user information), and GlideAjax (for asynchronous server calls).
• Server-Side APIs: These execute on the ServiceNow server, interacting directly with the database and business logic. This is where the magic of data manipulation happens! Key players here include GlideRecord (our main star!), GlideSystem (for logging, date/time, properties), and GlideAggregation.

Unveiling GlideRecord: Your Data’s Best Friend

Among the pantheon of Glide APIs, GlideRecord stands out as arguably the most crucial and frequently used. If you’re going to write any server-side script that touches data in ServiceNow, chances are you’ll be using GlideRecord.

What Exactly is GlideRecord and Why is it So Important?

GlideRecord is essentially a special JavaScript class that runs exclusively on the server side. Its primary purpose? To enable you to perform standard CRUD operations (Create, Read, Update, Delete) on ServiceNow database tables. It acts as an abstraction layer, allowing you to interact with rows and columns of your underlying database without ever having to write a single line of SQL. This means cleaner, safer, and more portable code within the ServiceNow ecosystem.

• Most Common API: You’ll see it everywhere – Business Rules, Script Includes, Fix Scripts, Workflows, Integrations.
• Server-Side Execution: It lives and breathes on the server, making it powerful for backend logic.
• SQL Generator: Behind the scenes, GlideRecord constructs and executes optimized SQL queries based on your JavaScript commands.
• CRUD Operations: Your go-to for adding, retrieving, modifying, or removing data.

The Architecture Behind the Scenes

Imagine you want to fetch a list of active incidents. Instead of directly hitting the database with a complex SQL query, you write a few lines of JavaScript using GlideRecord. GlideRecord then translates your JavaScript commands into the appropriate SQL query, sends it to the database, processes the results, and returns them to your script. It’s a beautiful, efficient dance:

Similarly, when you work with individual records, GlideRecord provides a direct mapping to the database table’s columns, allowing you to access and set field values as if they were properties of a JavaScript object.

A Crucial Heads-Up: Test Before You Deploy!

Before we dive into the exciting world of querying, here’s a golden rule that cannot be stressed enough: ALWAYS test your GlideRecord queries and operations on a non-production instance first!

An incorrectly constructed query – perhaps with a misspelled field name, an invalid operator, or a logical flaw – can lead to unexpected and potentially disastrous results. Running an `insert()`, `update()`, `deleteRecord()`, or `deleteMultiple()` method on a flawed query can lead to data loss, corruption, or unintended changes across your instance. Play it safe: sandbox your scripts, verify your results, and only then consider promoting them to production. Your data (and your colleagues) will thank you!

Throughout our exercises, we’ll be using the Script – Background application in ServiceNow. It’s a fantastic sandbox for testing server-side scripts without impacting users or other system processes directly. Just remember the testing mantra!

The Art of Querying: Getting Started with GlideRecord Methods

Let’s kick things off with the basics of retrieving data. The core methods you’ll use for querying are `query()`, `next()`, and `addQuery()`. Also, you’ll need a way to see your results, and `gs.print()` or `gs.info()` are your friends for server-side debugging.

Displaying Output with gs.print() and gs.info()

On the server side, you can’t just `console.log()` like in browser JavaScript. Instead, ServiceNow provides `gs.print()` and `gs.info()` (part of the GlideSystem API) to output messages to the Script Background window or system logs.

gs.print('Welcome to ServiceNow Academy');
gs.info('Welcome to ServiceNow Academy');
// Result in Script Background output:
// Welcome to ServiceNow Academy
// Welcome to ServiceNow Academy

They both work similarly, with `gs.info()` often used for informational messages that might appear in system logs, and `gs.print()` providing a direct output to your current session in the Script Background.

A Simple Program: Adding Numbers

Just to get our JavaScript muscles warmed up, here’s a quick example:

var a = 10;
var b = 20;
var c = a + b;
gs.print(a + b);
// Result: 30

Working with query() and next()

These two methods are the backbone of reading data with GlideRecord. `query()` executes the query you’ve built (or fetches all records if no specific query is added), and `next()` moves to the next record in the result set, returning `true` if there’s another record, and `false` if it’s the end.

Exercise 1: Printing All Incident Numbers

Let’s fetch and print the numbers of all incidents in your instance.

var inc = new GlideRecord('incident'); // Instantiate GlideRecord for the 'incident' table
inc.query(); // Execute the query (no conditions means fetch all)

while (inc.next()) { // Loop through each record found
    gs.print(inc.number); // Access the 'number' field of the current incident record
}
// Result: Will print the number (e.g., INC0000001, INC0000002, etc.) for every incident.

Explanation: We create a new `GlideRecord` object, specifying the `incident` table. `inc.query()` without any `addQuery()` calls before it means “give me all records.” The `while (inc.next())` loop is standard practice: it fetches the next record and continues as long as there are more records to process. Inside the loop, `inc.number` directly accesses the ‘number’ field of the current record.

Mastering Multiple Queries: Filtering Your Data

Now, let’s get serious about filtering. Rarely do you want *all* records. You usually need specific ones. This is where `addQuery()` and `addEncodedQuery()` become indispensable.

The Versatility of addQuery()

`addQuery()` allows you to add conditions to your GlideRecord query. You can use it in a few different formats, but the most common are `addQuery(fieldName, value)` and `addQuery(fieldName, operator, value)`.

Exercise 2: Displaying Priority 1 Incidents

Let’s find all incidents with a priority of ‘1 – Critical’.

var inc = new GlideRecord('incident');
inc.addQuery('priority', '1'); // Add a condition: where 'priority' field equals '1'
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - Priority: ' + inc.priority.getDisplayValue());
}
// Result: Prints incident numbers that have a priority of 1 (Critical).
// Example: INC0000005 - Priority: 1 - Critical

Explanation: We’ve now introduced `addQuery()`. This tells GlideRecord to filter the results. Notice I added `getDisplayValue()` for the priority to make the output more human-readable; without it, you’d likely see “1” if `priority` stores an integer.

Chaining Conditions: Multiple addQuery() Statements

One of the most common ways to build complex queries is by simply chaining multiple `addQuery()` statements. GlideRecord automatically interprets multiple `addQuery()` calls as an “AND” condition, meaning *all* conditions must be met for a record to be included in the result set.

Exercise 3: Incidents with Multiple Conditions (AND Logic)

Let’s find all *active* incidents with a *priority of 1* and a *category of ‘software’*. This is a classic example of working with multiple queries.

var inc = new GlideRecord('incident');
inc.addQuery('active', true);           // Query 1: Where 'active' is true
inc.addQuery('priority', '1');          // Query 2: AND 'priority' equals '1'
inc.addQuery('category', 'software');   // Query 3: AND 'category' equals 'software'
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints incident numbers and short descriptions for records that meet ALL three conditions.
// Example: INC0010020 - Issue with SAP login

Interview Relevance: This is a very common scenario. Be prepared to explain how multiple `addQuery()` statements combine their conditions.

The Power of addEncodedQuery() for Complex Filters

While chaining `addQuery()` is great, sometimes you need to construct truly complex queries with “OR” conditions, nested logic, or simply a long list of “AND” conditions. Manually writing these out with `addQuery()` can become cumbersome and error-prone. Enter `addEncodedQuery()` – your secret weapon for elegant, powerful queries.

An encoded query is a string representation of a filter that you typically build using the ServiceNow list interface. It’s concise and accurately reflects complex filter logic.

Exercise 4: Using addEncodedQuery() with a Generated Query

Let’s replicate the previous exercise, but using an encoded query.

1. Step 1: Navigate to the Incident list view. In your ServiceNow instance, type “incident.list” in the filter navigator and press Enter.
2. Step 2: Apply your conditions. Use the filter builder (the “funnel” icon) to set your conditions:
   • Active = true
   • AND Priority = 1 - Critical
   • AND Category = Software
3. Step 3: Click “Run”. This applies the filter to your list.
4. Step 4: Copy the query. Right-click on the breadcrumbs (e.g., “All > Active = true > …”) and select “Copy query”. This will copy the encoded query string to your clipboard. It will look something like `active=true^category=software^priority=1`.
5. Step 5: Use this query in your script.

var inc = new GlideRecord('incident');
inc.addEncodedQuery('active=true^category=software^priority=1'); // Paste your copied query here
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Same as Exercise 3, but achieved with a single addEncodedQuery() call.

Exercise 5: Storing Encoded Queries in Variables

For even cleaner code, especially if you reuse an encoded query, store it in a variable:

var myEncodedQuery = 'active=true^category=software^priority=1'; // Encoded query set to a variable
var inc = new GlideRecord('incident');
inc.addEncodedQuery(myEncodedQuery);
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints all records meeting the conditions specified in 'myEncodedQuery'.

Interview Relevance: A common interview question is “When would you use `addEncodedQuery()` over `addQuery()`?” The answer involves complexity (especially OR conditions) and reusability of a filter built in the UI.

Fine-Tuning Queries with Operators: addQuery(String, Operator, Value)

Beyond simple equality, `addQuery()` supports various operators for more nuanced filtering. This is where you can mimic SQL-like comparisons.

Common Operators (Numbers/Dates):

• `=` (equals)
• `!=` (not equals)
• `>` (greater than)
• `>=` (greater than or equal to)
• `<` (less than)
• `<=` (less than or equal to)

Common Operators (Strings – Must be uppercase):

• `=` (equals)
• `!=` (not equals)
• `IN` (value is in a list)
• `NOT IN` (value is not in a list)
• `STARTSWITH`
• `ENDSWITH`
• `CONTAINS`
• `DOES NOT CONTAIN`
• `INSTANCEOF` (checks if a record is of a specific class/table)

Exercise 6: Active Incidents with Priority <= 2

Let’s find active incidents with a priority of ‘1 – Critical’ or ‘2 – High’.

var inc = new GlideRecord('incident');
inc.addActiveQuery(); // Shortcut for 'active=true'
inc.addQuery('priority', '<=', 2); // Priority is less than or equal to 2
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - Priority: ' + inc.priority.getDisplayValue());
}
// Result: Prints active incidents with Priority 1 or 2.

Exercise 7: Combining Operators - Priority <= 2 AND Short Description Contains 'SAP'

Let's get more specific: active incidents with priority <= 2, *and* whose short description contains "SAP".

var inc = new GlideRecord('incident');
inc.addActiveQuery();
inc.addQuery('priority', '<=', 2);
inc.addQuery('short_description', 'CONTAINS', 'SAP'); // Case-sensitive by default!
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints incidents meeting both priority and short description criteria.

Exercise 8: Using the IN Operator with a List of Values

What if you want records where a field's value is one of several possibilities? The `IN` operator is perfect for this, especially with an array.

var categories = ['software', 'hardware']; // An array of categories
var inc = new GlideRecord('incident');
inc.addQuery('category', 'IN', categories); // Category is 'software' OR 'hardware'
inc.query();

while (inc.next()) {
    gs.print(inc.getValue('number') + ' - ' + inc.getValue('short_description') + ' (Category: ' + inc.getDisplayValue('category') + ')');
}
// Result: Prints incidents where the category is either 'software' or 'hardware'.

Exercise 9: Using the STARTSWITH Operator

To find records where a string field begins with a specific prefix:

var inc = new GlideRecord('incident');
inc.addQuery('category', 'STARTSWITH', 'net'); // Category starts with 'net' (e.g., 'network')
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - Category: ' + inc.category.getDisplayValue());
}
// Result: Prints incidents with categories like 'network', 'net-services', etc.

Convenience Methods and Query Control

ServiceNow offers several convenient methods to streamline common query patterns and control how many records you fetch or how they're ordered.

addActiveQuery() and addInactiveQuery()

Instead of `addQuery('active', true)` or `addQuery('active', false)`, these methods offer a neat shortcut.

Exercise 10: Active Incidents with Priority 1

var inc = new GlideRecord('incident');
inc.addActiveQuery(); // Automatically adds 'active=true'
inc.addQuery('priority', 1);
inc.query();

while (inc.next()) {
    gs.info(inc.number);
}
// Result: Prints active incidents with priority 1.

Exercise 11: Inactive Incidents with Priority 1

var inc = new GlideRecord('incident');
inc.addInactiveQuery(); // Automatically adds 'active=false'
inc.addQuery('priority', 1);
inc.query();

while (inc.next()) {
    gs.print(inc.number);
}
// Result: Prints inactive (e.g., closed) incidents with priority 1.

getEncodedQuery(): Peeking at Your Query

This method is incredibly useful for debugging. It returns the actual encoded query string that your GlideRecord object has constructed.

Exercise 12: Getting the Encoded Query from Your Script

var inc = new GlideRecord('incident');
inc.addEncodedQuery('active=true^category=software^priority=1');
inc.query(); // Note: query() usually needs to run before getEncodedQuery() accurately reflects the final query.

// Although you queried, getEncodedQuery() will give you what you explicitly set or implicitly built.
// To get the full query *after* it's been processed, sometimes you need to get the first record or similar.
// However, it reliably shows what you *intended* to query.
gs.print(inc.getEncodedQuery());
// Result: Prints the string 'active=true^category=software^priority=1'

Sorting Your Results: orderBy() and orderByDesc()

Displaying data in a meaningful order is often crucial. These methods help you sort your results in ascending or descending order based on a specified field.

Exercise 13: Order By Short Description (Ascending)

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.addQuery('category', 'software');
inc.orderBy('short_description'); // Sort by short_description in ascending order
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints incidents sorted by their short description alphabetically (A-Z).

Exercise 14: Order By Short Description (Descending)

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.addQuery('category', 'software');
inc.orderByDesc('short_description'); // Sort by short_description in descending order
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints incidents sorted by their short description reverse-alphabetically (Z-A).

Limiting the Load: setLimit()

For performance and efficiency, especially with large tables, `setLimit()` is your friend. It fetches only a specified number of records.

Exercise 15: Displaying the Latest 10 Incidents

var inc = new GlideRecord('incident');
inc.orderByDesc('sys_created_on'); // Order by creation date descending to get latest
inc.setLimit(10); // Limit results to the first 10
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description + ' (Created: ' + inc.sys_created_on + ')');
}
// Result: Prints the 10 most recently created incidents.

Troubleshooting Tip: If your script is slow or hitting memory limits with huge datasets, `setLimit()` (and filtering with `addQuery()`) is often the first optimization to consider.

Grabbing Specifics: get()

When you know the `sys_id` or another unique field (like `number` for incidents), `get()` is a direct way to fetch a single record without a `while` loop.

Exercise 16: Getting a Record by Number or Sys_ID

var inc = new GlideRecord('incident');
inc.get('number', 'INC0009005'); // Fetch the incident with this number
gs.print('Sys_ID for INC0009005: ' + inc.sys_id);
// Result: Prints the sys_id corresponding to INC0009005.

// Example 2: Getting by sys_id (often just inc.get(sys_id) is enough)
var inc2 = new GlideRecord('incident');
var specificSysID = 'a1234b5678c90d123e45f67890a123bc'; // Replace with an actual sys_id from your instance
inc2.get(specificSysID); // Fetch the incident with this sys_id
if (inc2.isValidRecord()) { // Always good to check if the record was found
    gs.print('Incident Number for ' + specificSysID + ': ' + inc2.number);
} else {
    gs.print('No record found with sys_id: ' + specificSysID);
}
// Result: Prints the incident number for the given sys_id.

Windowing Your View: chooseWindow()

Less commonly used but powerful for processing records in batches, `chooseWindow(firstRow, lastRow)` specifies a range of records to retrieve from the query result set (0-indexed). It includes the first value and excludes the second.

Exercise 17: Displaying Records from a Specific Range

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.addActiveQuery();
inc.chooseWindow(3, 7); // Include records at index 3, 4, 5, 6 (4 records total)
inc.query();

while (inc.next()) {
    gs.print(inc.number);
}
// Result: Prints 4 incident numbers starting from the 4th record of the filtered set.

Counting Your Records: getRowCount()

To quickly find out how many records match your query, use `getRowCount()`. Remember to call `query()` *before* `getRowCount()` for accurate results.

Exercise 18: Getting the Total Count of Incidents

var inc = new GlideRecord('incident');
inc.query(); // Execute the query first
gs.print('Total incidents: ' + inc.getRowCount());
// Result: Prints the total number of records in the 'incident' table.

Exercise 19: Counting Active Users

var grUser = new GlideRecord('sys_user');
grUser.addQuery('active', true);
grUser.query();
gs.print('Active users are: ' + grUser.getRowCount());
// Result: Prints the number of active user records.

Extracting Field Values: getValue() vs. getDisplayValue()

A crucial distinction! Accessing a field directly (e.g., `inc.priority`) often gives you the *actual* stored value (e.g., '1', '2'). `getDisplayValue()` fetches the human-readable label (e.g., '1 - Critical', '2 - High'). `getValue()` is explicitly for the stored value.

Exercise 20: Using getValue()

var inc = new GlideRecord('incident');
inc.addActiveQuery();
inc.query();
while (inc.next()) {
    gs.print(inc.getValue('short_description')); // Gets the raw string value
}
// Result: Prints the short descriptions as they are stored.

Exercise 21: Using getDisplayValue()

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.query();
while (inc.next()) {
    gs.print(inc.priority.getDisplayValue()); // Gets the human-readable label for priority
}
// Result: Prints '1 - Critical' (or whatever the display value is).
// You can also use inc.getDisplayValue('priority') for the same effect.

Checking for More: hasNext()

The `hasNext()` method, implicitly used by `while(inc.next())`, checks if there are more records available in the result set. It returns `true` or `false`.

Exercise 22: Understanding hasNext()

var inc = new GlideRecord('incident');
inc.addQuery('number', 'INC0000001'); // Query for a specific incident
inc.query();
// At this point, the query has run, but inc.next() hasn't been called yet.
// If the record exists, hasNext() will be true.
gs.print('Does the query have at least one result? ' + inc.hasNext());
inc.next(); // Move to the first record
gs.print('After moving to the first record, are there more? ' + inc.hasNext());
// Result: True (if record exists), then False (if only one record exists).

Unique Identifiers: getUniqueValue()

This method conveniently returns the `sys_id` of the current record. It's often used when you need to link to or reference a specific record.

Exercise 23: Getting the Sys_ID

var inc = new GlideRecord('incident');
inc.query();
if (inc.next()) { // Move to the first record
    var uniqueValue = inc.getUniqueValue();
    gs.print('Sys_ID of the first incident: ' + uniqueValue);
}
// Result: Prints the sys_id of the first incident found.

CRUD Operations and Record Management

Beyond just reading, GlideRecord empowers you to create, update, and delete records, giving you full control over your ServiceNow data.

Creating New Records: initialize(), setValue(), insert()

The process for creating a new record is straightforward: `initialize()` sets up a blank record, you set its field values, and then `insert()` saves it to the database.

Exercise 24: Creating a New Incident

var inc = new GlideRecord('incident');
inc.initialize(); // Prepares a new, empty incident record (like clicking "New" on a form)
inc.category = 'network'; // Set field values directly
inc.short_description = 'Critical VPN Issue - Cannot connect to corporate network.';
inc.priority = 1; // Set priority to 1 - Critical
inc.insert(); // Save the new record to the database
gs.print('New Incident Created: ' + inc.number);
// Result: Creates a new incident record and prints its generated number (e.g., INC0010045).

You can also use `setValue()` for setting field values, which can be useful when field names are dynamic:

Exercise 25: Using setValue() for Creation

var inc = new GlideRecord('incident');
inc.initialize();
inc.setValue('category', 'network');
inc.setValue('short_description', 'Critical VPN Issue');
inc.insert();
gs.print('Category is ' + inc.category.getDisplayValue() + ' and issue is: ' + inc.short_description);
// Result: Creates a new incident and prints its category and short description.

isNewRecord() and newRecord()

`newRecord()` creates a new GlideRecord and assigns a unique ID, effectively preparing it for insertion. `isNewRecord()` checks if the current GlideRecord object represents a record that hasn't been saved to the database yet.

Exercise 26: Checking if a Record is New

var inc = new GlideRecord('incident');
inc.newRecord(); // Creates a new GlideRecord instance ready for insertion
gs.info('Is this a new record? ' + inc.isNewRecord());
// Result: True

Updating Records: update() and updateMultiple()

To modify existing records, you first query for them, then set the new values, and finally call `update()` (for a single record) or `updateMultiple()` (for all records matching your query).

Exercise 27: Updating a Single Record

var inc = new GlideRecord('incident');
inc.get('number', 'INC0000057'); // Get the specific incident to update
if (inc.isValidRecord()) { // Check if the record was found
    inc.setValue('state', 2); // Set 'state' to 'In Progress' (assuming '2' is the value for In Progress)
    inc.update(); // Save the changes to this single record
    gs.print('Incident ' + inc.number + ' updated to state: ' + inc.state.getDisplayValue());
} else {
    gs.print('Incident INC0000057 not found.');
}
// Result: Updates INC0000057's state and prints a confirmation.

Exercise 28: Updating Multiple Records

Be extremely cautious with `updateMultiple()`! It affects *all* records that match your query.

var inc = new GlideRecord('incident');
inc.addQuery('category', 'hardware'); // Query for all incidents with category 'hardware'
inc.setValue('category', 'software'); // Set their category to 'software'
inc.updateMultiple(); // Apply this change to ALL matching records
gs.print('All hardware incidents updated to software category.');
// Result: Changes the category for all incidents that were 'hardware' to 'software'.

Deleting Records: deleteRecord() and deleteMultiple()

These methods permanently remove data. Use with extreme caution and always test thoroughly in non-production!

Exercise 29: Deleting a Single Record

var inc = new GlideRecord('incident');
inc.get('number', 'INC0010013'); // Get the specific incident to delete
if (inc.isValidRecord()) {
    inc.deleteRecord(); // Delete this single record
    gs.print('Incident ' + inc.number + ' deleted.');
} else {
    gs.print('Incident INC0010013 not found for deletion.');
}
// Result: Deletes INC0010013 and prints a confirmation.

Exercise 30: Deleting Multiple Records

This is the most dangerous! It deletes every record matching your query.

var inc = new GlideRecord('incident');
inc.addQuery('priority', 4); // Query for all incidents with priority 4
inc.query(); // Execute the query
var deletedCount = inc.getRowCount(); // Get the count before deleting
inc.deleteMultiple(); // Delete all matching records
gs.print(deletedCount + ' incidents with priority 4 deleted.');
// Result: Deletes all incidents with priority 4 and prints how many were deleted.

Handling Nulls: addNullQuery() and addNotNullQuery()

These are convenient shortcuts for filtering records based on whether a field's value is empty or not.

Exercise 31: Records with Null Short Description

var inc = new GlideRecord('incident');
inc.addNullQuery('short_description'); // Find records where short_description is empty/null
inc.query();
while (inc.next()) {
    gs.print(inc.number);
}
// Result: Prints incident numbers that have an empty short_description.

Exercise 32: Records with Non-Null Short Description

var inc = new GlideRecord('incident');
inc.addNotNullQuery('short_description'); // Find records where short_description is NOT empty/null
inc.query();
while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints incident numbers and short descriptions for records that actually have a value.

Record Metadata, Security, and Advanced Controls

GlideRecord isn't just about data; it also provides ways to inspect records, check permissions, and control system behavior.

isValid(), isValidField(), isValidRecord()

These methods help you build robust scripts by verifying the existence of tables, fields, or specific records.

Exercise 33: Checking Table and Field Validity

var inc = new GlideRecord('incident');
gs.print('Is "incident" a valid table? ' + inc.isValid()); // Checks if the table exists
gs.print('Does "incident" table have a "category" field? ' + inc.isValidField('category')); // Checks if field exists
// Result: True, True

var fakeGR = new GlideRecord('uday'); // A non-existent table
gs.print('Is "uday" a valid table? ' + fakeGR.isValid());
// Result: False

Exercise 34: Checking Record Validity

var inc = new GlideRecord('incident');
inc.get('number', 'INC0010012'); // Try to get a specific incident
gs.print(inc.number + ' exists: ' + inc.isValidRecord()); // Checks if the get() operation found a record
// Result: INC0010012 exists: True (assuming it exists)

Access Control Checks: canCreate(), canRead(), canWrite(), canDelete()

These are invaluable for scripts that need to respect ServiceNow's Access Control Lists (ACLs). They tell you if the currently logged-in user (or system user if running in a business rule) has permission to perform an action on the record.

Exercise 35: Checking Permissions

var inc = new GlideRecord('incident');
// Note: These methods check permissions based on the *current* user's context.
gs.print('Can create incident records? ' + inc.canCreate());
gs.print('Can read incident records? ' + inc.canRead());
gs.print('Can write to incident records? ' + inc.canWrite());
gs.print('Can delete incident records? ' + inc.canDelete());
// Result: True (assuming your user has the necessary roles like 'itil').

Controlling System Fields and Workflows: autoSysFields() and setWorkflow()

These are advanced methods, often used in integrations or data imports, where you want to bypass standard system behaviors.

• autoSysFields(false): Prevents system fields like `sys_updated_on`, `sys_updated_by`, `sys_mod_count`, `sys_created_on`, `sys_created_by` from being automatically updated when you call `update()`. This is useful for preserving historical data during migrations or specific integrations. (Note: This might not work in Scoped Applications).
• setWorkflow(false): Prevents Business Rules, Workflow Activities, and other engine-driven automation from running when `update()` or `insert()` is called. Use with extreme caution, as it bypasses critical business logic!

Exercise 36: Updating Records Without Triggering System Fields or Workflows

var inc = new GlideRecord('incident');
inc.addQuery('state', 1); // Find incidents in 'New' state (value '1')
inc.query();

while (inc.next()) {
    inc.autoSysFields(false); // Do not update system fields (updated_by, updated_on, etc.)
    inc.setWorkflow(false); // Do not run business rules, workflows
    inc.setValue('state', 2); // Change state to 'In Progress' (value '2')
    inc.update();
}
gs.print('Incidents in state "New" updated to "In Progress" without system field or workflow updates.');
// Result: Updates records but leaves audit fields like 'Updated' unchanged, and bypasses business logic.

Joining the Dots: addJoinQuery()

`addJoinQuery()` allows you to query records from one table based on conditions in a related table. It performs an inner join.

Exercise 37: Finding Problems with Associated Incidents

var prob = new GlideRecord('problem');
// Find problems where the 'opened_by' user in the problem table
// is also the 'caller_id' of an associated incident.
prob.addJoinQuery('incident', 'opened_by', 'caller_id');
prob.query();

while (prob.next()) {
    gs.print('Problem with associated incident: ' + prob.number);
}
// Result: Displays problem records that have at least one incident where the problem's opener is the incident's caller.

Building Robust Logic: setAbortAction() for Validation

`setAbortAction(true)` is often used in server-side scripts (like Business Rules) to stop the current database operation (insert, update, delete) if a validation check fails. This prevents invalid data from being saved.

Exercise 38: Date Validation with setAbortAction()

Imagine a scenario where a custom table `u_my_task` has `u_date1` (start date) and `u_date2` (end date) fields, and `u_date1` must always be before `u_date2`. This script would typically be a `before insert/update` Business Rule.

if ((!current.u_date1.nil()) && (!current.u_date2.nil())) { // Check if both dates are populated
    // Get numeric values for comparison (GlideDateTime objects)
    var start = current.u_date1.getGlideObject().getNumericValue();
    var end = current.u_date2.getGlideObject().getNumericValue();

    if (start > end) { // If start date is after end date
        gs.addInfoMessage('Start date must be before end date.'); // Inform the user
        current.u_date1.setError('Start date must be before end date.'); // Highlight the problematic field
        current.setAbortAction(true); // Prevent the record from being saved
    }
}
// Result: If an attempt is made to save u_my_task with u_date1 > u_date2,
// an info message appears, u_date1 field gets an error, and the save operation is cancelled.

Troubleshooting Common GlideRecord Issues

Even seasoned developers run into snags. Here are some common GlideRecord issues and how to tackle them:

• No Records Returned:
  • Check your query conditions: Are they too restrictive? Are field names spelled correctly? (e.g., `addQuery('short_descriptoin', '...')` instead of `short_description`).
  • Data mismatch: Are you querying for `priority = '1'` when the field stores `1 - Critical` or vice-versa? Use `getDisplayValue()` for display, but often `getValue()` for actual querying.
  • Table name: Is `new GlideRecord('incident')` correct, or should it be a different table? Use `isValid()` to check.
• Infinite Loop:
  • Forgetting `inc.next()` inside your `while` loop is a classic. The loop condition will always be true, and your script will hang.
• Performance Problems:
  • Large datasets: Are you querying for millions of records? Use `setLimit()` or add more specific `addQuery()` conditions to narrow down your results.
  • Unindexed fields: Queries on unindexed fields can be slow. Check field definitions.
  • `gs.print()`/`gs.info()` inside loops: Excessive logging inside a loop processing many records can slow things down. Remove or limit these for production scripts.
• Permissions Denied (Operations Fail):
  • If `insert()`, `update()`, or `delete()` fails, it's often an Access Control List (ACL) issue. The user (or system context) running the script doesn't have the necessary roles or conditions met. Use `canCreate()`, `canWrite()`, etc., to debug.
• Unintended Data Changes:
  • This usually stems from an incorrect query for `updateMultiple()` or `deleteMultiple()`. Always verify your `addQuery()` conditions thoroughly before running these bulk operations.

Interview Questions You Might Face

GlideRecord is fundamental, so expect questions about it during ServiceNow developer interviews. Here are some common ones:

• What's the difference between `addQuery()` and `addEncodedQuery()`? When would you use each? (Hint: Flexibility vs. Complexity/UI-generated queries)
• Explain `getValue()` vs. `getDisplayValue()`. (Hint: Stored value vs. human-readable label)
• How do you create a new record using GlideRecord? What methods are involved? (Hint: `initialize()`, `setValue()` or direct field assignment, `insert()`)
• When would you use `setWorkflow(false)` or `autoSysFields(false)`? What are the implications? (Hint: Integrations/migrations, bypassing business rules/audit logs, caution!)
• Why is `inc.next()` crucial in a GlideRecord query loop? (Hint: Iteration, fetching next record, preventing infinite loops)
• How would you ensure your GlideRecord script performs well on large tables? (Hint: `setLimit()`, effective `addQuery()` conditions, `orderBy()` on indexed fields)
• How do you ensure a record exists before attempting to update or delete it? (Hint: `isValidRecord()`, `if (gr.get(sys_id))` check)

Understanding the Glide API Ecosystem

At its core, ServiceNow is built on a robust platform that allows for extensive customization. While the platform offers plenty of out-of-the-box functionality, developers often need to tweak behaviors, integrate with other systems, or build entirely new features. This is where the Glide APIs come into play.

Think of Glide APIs as your Swiss Army knife for interacting with the ServiceNow platform programmatically. Instead of writing raw SQL queries – which we generally can't do directly in ServiceNow for security and abstraction reasons – Glide APIs provide a structured, JavaScript-friendly way to perform database operations, manipulate records, and even interact with the user interface. Each API is packed with methods designed to perform specific tasks, giving you immense flexibility.

Types of Glide APIs: A Quick Glimpse

The Glide API landscape is vast, broadly categorized into Client-Side and Server-Side APIs, reflecting where your script executes:

• Client-Side APIs: These run in the user's browser, typically affecting the UI or user experience. Examples include GlideForm (for manipulating forms), GlideUser (for user information), and GlideAjax (for asynchronous server calls).
• Server-Side APIs: These execute on the ServiceNow server, interacting directly with the database and business logic. This is where the magic of data manipulation happens! Key players here include GlideRecord (our main star!), GlideSystem (for logging, date/time, properties), and GlideAggregation.

Unveiling GlideRecord: Your Data's Best Friend

Among the pantheon of Glide APIs, GlideRecord stands out as arguably the most crucial and frequently used. If you're going to write any server-side script that touches data in ServiceNow, chances are you'll be using GlideRecord.

What Exactly is GlideRecord and Why is it So Important?

GlideRecord is essentially a special JavaScript class that runs exclusively on the server side. Its primary purpose? To enable you to perform standard CRUD operations (Create, Read, Update, Delete) on ServiceNow database tables. It acts as an abstraction layer, allowing you to interact with rows and columns of your underlying database without ever having to write a single line of SQL. This means cleaner, safer, and more portable code within the ServiceNow ecosystem.

• Most Common API: You'll see it everywhere – Business Rules, Script Includes, Fix Scripts, Workflows, Integrations.
• Running from server side: It lives and breathes on the server, making it powerful for backend logic.
• Used to generate SQL Queries: Behind the scenes, GlideRecord constructs and executes optimized SQL queries based on your JavaScript commands.
• Perform CRUD operations: Your go-to for adding, retrieving, modifying, or removing data.

GlideRecord's Inner Workings

Imagine you want to fetch a list of active incidents. Instead of directly hitting the database with a complex SQL query, you write a few lines of JavaScript using GlideRecord. GlideRecord then translates your JavaScript commands into the appropriate SQL query, sends it to the database, processes the results, and returns them to your script. It's a beautiful, efficient dance:

Mapping Our Data: How GlideRecord Connects

When you work with individual records, GlideRecord provides a direct mapping to the database table's columns, allowing you to access and set field values as if they were properties of a JavaScript object. This seamless integration simplifies data manipulation significantly.

The Art of Querying: Getting Started with GlideRecord Methods

Let's kick things off with the basics of retrieving data. The core methods you'll use for querying are query(), next(), and addQuery(). Also, you'll need a way to see your results, and gs.print() or gs.info() are your friends for server-side debugging.

Displaying Output with gs.print() and gs.info()

On the server side, you can't just console.log() like in browser JavaScript. Instead, ServiceNow provides gs.print() and gs.info() (part of the GlideSystem API) to output messages to the Script Background window or system logs.

gs.print('Welcome to ServiceNow Academy');
gs.info('Welcome to ServiceNow Academy');
// Result in Script Background output:
// Welcome to ServiceNow Academy
// Welcome to ServiceNow Academy

They both work similarly, with gs.info() often used for informational messages that might appear in system logs, and gs.print() providing a direct output to your current session in the Script Background.

A Simple Program: Adding Numbers

Just to get our JavaScript muscles warmed up, here's a quick example:

var a = 10;
var b = 20;
var c = a + b;
gs.print(a + b);
// Result: 30

Working with query() method

The query() method is essential; it executes the query you've built (or fetches all records if no specific query is added). When combined with next(), it becomes a powerful tool for iterating through your results.

Exercise 1: Printing All Incident Numbers

Let's fetch and print the numbers of all incidents in your instance.

var inc = new GlideRecord('incident'); // Instantiate GlideRecord for the 'incident' table
// GlideRecord is the main object, and 'incident' is the table name.
inc.query(); // Execute the query (no conditions means fetch all records from the table)

while (inc.next()) { // Loop through each record found. The loop continues as long as there are more records.
    gs.print(inc.number); // Access the 'number' field of the current incident record and print it.
}
// Result: Will print the number (e.g., INC0000001, INC0000002, etc.) for every incident in the Incident Table.

Explanation: We create a new GlideRecord object, specifying the incident table. inc.query() without any addQuery() calls before it means "give me all records." The while (inc.next()) loop is standard practice: it fetches the next record and continues as long as there are more records to process. Inside the loop, inc.number directly accesses the 'number' field of the current record.

Mastering Multiple Queries: Filtering Your Data

Now, let's get serious about filtering. Rarely do you want all records. You usually need specific ones. This is where addQuery() and addEncodedQuery() become indispensable.

The Versatility of addQuery() and next() and while methods

addQuery() allows you to add conditions to your GlideRecord query. You can use it in a few different formats, but the most common are addQuery(fieldName, value) and addQuery(fieldName, operator, value).

Exercise 2: Displaying Priority 1 Incidents

Let's find all incidents with a priority of '1 - Critical'.

var inc = new GlideRecord('incident');
inc.addQuery('priority', '1'); // Add a condition: where 'priority' field equals '1'
inc.query();

while (inc.next()) { // Loop through the filtered results
    gs.print(inc.number + ' - Priority: ' + inc.priority.getDisplayValue());
}
// Result: Prints incident numbers that have a priority of 1 (Critical).
// Example: INC0000005 - Priority: 1 - Critical

Explanation: We've now introduced addQuery(). This tells GlideRecord to filter the results. Notice I added getDisplayValue() for the priority to make the output more human-readable; without it, you'd likely see "1" if priority stores an integer.

Chaining Conditions: Multiple addQuery() Statements

One of the most common ways to build complex queries is by simply chaining multiple addQuery() statements. GlideRecord automatically interprets multiple addQuery() calls as an "AND" condition, meaning all conditions must be met for a record to be included in the result set.

Exercise 3: Incidents with Multiple Conditions (AND Logic)

Let's find all active incidents with a priority of 1 and a category of 'software'. This is a classic example of working with multiple queries.

var inc = new GlideRecord('incident');
inc.addQuery('active', true);           // Query 1: Where 'active' is true
inc.addQuery('priority', '1');          // Query 2: AND 'priority' equals '1'
inc.addQuery('category', 'software');   // Query 3: AND 'category' equals 'software'
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints incident numbers and short descriptions for records that meet ALL three conditions.
// Example: INC0010020 - Issue with SAP login

The Power of addEncodedQuery() for Complex Filters

While chaining addQuery() is great, sometimes you need to construct truly complex queries with "OR" conditions, nested logic, or simply a long list of "AND" conditions. Manually writing these out with addQuery() can become cumbersome and error-prone. Enter addEncodedQuery() – your secret weapon for elegant, powerful queries.

An encoded query is a string representation of a filter that you typically build using the ServiceNow list interface. It's concise and accurately reflects complex filter logic.

Exercise 4: Using addEncodedQuery() with a Generated Query

Let's replicate the previous exercise, but using an encoded query.

1. Step 1: Navigate to the Incident list view. In your ServiceNow instance, type "incident.list" in the filter navigator and press Enter.
2. Step 2: Apply your conditions. Use the filter builder (the "funnel" icon or the condition builder) to set your conditions:
   • Active = true
   • AND Priority = 1 - Critical
   • AND Category = Software
3. Step 3: Click "Run". This applies the filter to your list.
4. Step 4: Copy the query. Right-click on the breadcrumbs (e.g., "All > Active = true > ...") and select "Copy query". This will copy the encoded query string to your clipboard. It will look something like active=true^category=software^priority=1.
5. Step 5: Use this query in your script.

var inc = new GlideRecord('incident');
inc.addEncodedQuery('active=true^category=software^priority=1'); // Paste your copied query here
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Same as Exercise 3, but achieved with a single addEncodedQuery() call.

Exercise 5: Storing Encoded Queries in Variables

For even cleaner code, especially if you reuse an encoded query, store it in a variable:

var ecq = 'active=true^category=software^priority=1'; // Encoded query set to a variable
var inc = new GlideRecord('incident');
inc.addEncodedQuery(ecq);
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Prints all records where this meet 'active=true^category=software^priority=1'.

Fine-Tuning Queries with Operators: addQuery(String, Operator, Value)

Beyond simple equality, addQuery() supports various operators for more nuanced filtering. This is where you can mimic SQL-like comparisons.

Common Operators (Numbers/Dates):

• `=` (equals)
• `!=` (not equals)
• `>` (greater than)
• `>=` (greater than or equal to)
• `<` (less than)
• `<=` (less than or equal to)

Common Operators (Strings - Must be uppercase):

• `=` (equals)
• `!=` (not equals)
• `IN` (value is in a list)
• `NOT IN` (value is not in a list)
• `STARTSWITH`
• `ENDSWITH`
• `CONTAINS`
• `DOES NOT CONTAIN`
• `INSTANCEOF` (checks if a record is of a specific class/table)

Exercise 6: Active and Priority is less than or equal to 2

Let's find active incidents with a priority of '1 - Critical' or '2 - High'.

var inc = new GlideRecord('incident');
inc.addActiveQuery(); // Shortcut for 'active=true'
inc.addQuery('priority', '<=', 2); // Priority is less than or equal to 2
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - Priority: ' + inc.priority.getDisplayValue());
}
// Result: Prints active incidents like "INC0000001 - Priority: 1 - Critical" or "INC0000002 - Priority: 2 - High".

Exercise 7: Working with SQL operators <= and CONTAINS

Let's get more specific: active incidents with priority <= 2, and whose short description contains "SAP".

var inc = new GlideRecord('incident');
inc.addActiveQuery();
inc.addQuery('priority', '<=', 2);
inc.addQuery('short_description', 'CONTAINS', 'SAP'); // Case-sensitive by default!
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' ' + inc.short_description);
}
// Result: Prints all records where our condition meet like (<=2 and CONTAINS 'SAP').

Exercise 8: Working with IN operator and print category of Software and Hardware

What if you want records where a field's value is one of several possibilities? The IN operator is perfect for this, especially with an array.

var cat = ['software', 'hardware']; // An array of categories
var inc = new GlideRecord('incident');
inc.addQuery('category', 'IN', cat); // Category is 'software' OR 'hardware'
inc.query();

while (inc.next()) {
    gs.print(inc.getValue('number') + ' ' + inc.getValue('short_description') + ' (Category: ' + inc.getDisplayValue('category') + ')');
}
// Result: Prints incidents where the category is either 'Software' or 'Hardware'.

Exercise 9: Working with STARTSWITH Operator

To find records where a string field begins with a specific prefix:

var inc = new GlideRecord('incident');
inc.addQuery('category', 'STARTSWITH', 'net'); // Category starts with 'net' (e.g., 'network')
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' - Category: ' + inc.category.getDisplayValue());
}
// Result: Prints incidents with categories like 'network', 'net-services', etc.

Convenience Methods and Query Control

ServiceNow offers several convenient methods to streamline common query patterns and control how many records you fetch or how they're ordered.

addActiveQuery() and addInactiveQuery()

Instead of addQuery('active', true) or addQuery('active', false), these methods offer a neat shortcut.

Exercise 10: Instead of use active=true this method directly we can use addActiveQuery

var inc = new GlideRecord('incident');
inc.addActiveQuery(); // Automatically adds 'active=true'
inc.addQuery('priority', 1);
inc.query();

while (inc.next()) {
    gs.info(inc.number);
}
// Result: Print all records where active is true and priority -1.

Exercise 11: Instead of use active=false this method directly we can use addInactiveQuery

var inc = new GlideRecord('incident');
inc.addInactiveQuery(); // Automatically adds 'active=false' (Opposite of active query)
inc.addQuery('priority', 1);
inc.query();

while (inc.next()) {
    gs.print(inc.number);
}
// Result: Print only inactive Records like Incident state is Closed.

getEncodedQuery(): Peeking at Your Query

This method is incredibly useful for debugging. It returns the actual encoded query string that your GlideRecord object has constructed based on your addQuery or addEncodedQuery calls.

Exercise 12: getEncodedQuery from our code

var inc = new GlideRecord('incident');
inc.addEncodedQuery('active=true^category=software^priority=1');
inc.query(); // Although you queried, getEncodedQuery() will give you what you explicitly set or implicitly built.

// It reliably shows what you *intended* to query.
gs.print(inc.getEncodedQuery());
// Example: active=true^category=software^priority=1
// Result: Print our encodedQuery.

Sorting Your Results: orderBy() and orderByDesc()

Displaying data in a meaningful order is often crucial. These methods help you sort your results in ascending or descending order based on a specified field.

Exercise 13: Display all records in order wise (Ascending) it depends on field values

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.addQuery('category', 'software');
inc.orderBy('short_description'); // Sort by short_description in ascending order
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' ' + inc.short_description);
}
// Result: Print all incidents order wise depends on Short Description.

Exercise 14: Display all records in order wise (Descending) it depends on field values

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.addQuery('category', 'software');
inc.orderByDesc('short_description'); // Sort by short_description in descending order
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' ' + inc.short_description);
}
// Result: Print all records in descending order (short_description).

Limiting the Load: setLimit()

For performance and efficiency, especially with large tables, setLimit() is your friend. It fetches only a specified number of records.

Exercise 15: Display limited records from specified table

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.orderByDesc('sys_created_on'); // Order by creation date descending to get latest
inc.setLimit(10); // Limit results to the first 10
inc.query();

while (inc.next()) {
    gs.print(inc.number + ' ' + inc.short_description);
}
// Result: Print only latest 10 records created from given table (based on sys_created_on and priority=1).

Grabbing Specifics: get() Method

When you know the sys_id or another unique field (like number for incidents), get() is a direct way to fetch a single record without a while loop. It returns `true` if the record is found, `false` otherwise.

Exercise 16: Get record sys_id depends on INC number or Get incident record number depends on sys_id

var inc = new GlideRecord('incident');
inc.get('number', 'INC0009005'); // Fetch the incident with this number
gs.print(inc.sys_id);
// Result: Print sys_id related to incident number.

// Example 2: Getting by sys_id
var inc2 = new GlideRecord('incident');
var specificSysID = 'a1234b5678c90d123e45f67890a123bc'; // Replace with an actual sys_id from your instance
inc2.get(specificSysID); // Fetch the incident with this sys_id
if (inc2.isValidRecord()) { // Always good to check if the record was found
    gs.print('Incident number related to ' + specificSysID + ': ' + inc2.number);
} else {
    gs.print('No record found with sys_id: ' + specificSysID);
}
// Result: Print Incident number related to sys_id.

Windowing Your View: chooseWindow() method

Less commonly used but powerful for processing records in batches, `chooseWindow(firstRow, lastRow)` specifies a range of records to retrieve from the query result set (0-indexed). It includes the first value and excludes the second.

Exercise 17: Display records between two numbers

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.addActiveQuery();
inc.chooseWindow(3, 7); // include first value, exclude second value (so records at index 3, 4, 5, 6)
inc.query();

while (inc.next()) {
    gs.print(inc.number);
}
// Result: Print records from number 3 to 7 (4 records).

Counting Your Records: getRowCount() method

To quickly find out how many records match your query, use `getRowCount()`. Remember to call `query()` *before* `getRowCount()` for accurate results.

Exercise 18: Display all records from particular table (Incident)

var inc = new GlideRecord('incident');
inc.query(); // Execute the query first
gs.print(inc.getRowCount());
// Result: Print number of records in particular table.

Exercise 19: Display all active users in our sys_user tables

var grUser = new GlideRecord('sys_user');
grUser.addQuery('active', true);
grUser.query();
gs.print('Active users are: ' + grUser.getRowCount());
// Result: Print number of active users in sys_user table.

Getting the Table Name: getTableName() method

A simple method to retrieve the name of the table associated with the current GlideRecord object.

Exercise 20: This method is used to get glide record table name

var inc = new GlideRecord('change_request');
gs.print(inc.getTableName());
// Result: Display current table name from glide record (e.g., 'change_request').

Extracting Field Values: getValue() method

getValue() fetches the raw, stored value of a specified field. This is useful when you need the internal representation rather than the display label.

Exercise 21: Get value of particular field in the table

var inc = new GlideRecord('incident');
inc.addQuery('active', true);
inc.query();
while (inc.next()) {
    gs.print(inc.getValue('short_description')); // Gets the raw string value
}
// Result: Print the value of short_description field from particular table.

Getting Display Values: getDisplayValue() method

This method fetches the human-readable label or display value of a field, which can be different from its actual stored value (e.g., for choice lists, reference fields).

Exercise 22: Print display value instead of actual value

var inc = new GlideRecord('incident');
inc.addQuery('priority', 1);
inc.query();
while (inc.next()) {
    gs.print(inc.priority.getDisplayValue()); // Gets the human-readable label for priority
}
// Result: Print display value of respective field (e.g., "1 - Critical").
// You can also use inc.getDisplayValue('priority') for the same effect.

Checking for More: hasNext() method

The `hasNext()` method, implicitly used by `while(inc.next())`, checks if there are more records available in the result set. It returns `true` or `false`.

Exercise 23: This method will return true if iterator have more elements.

var inc = new GlideRecord('incident');
inc.query();
// At this point, the query has run, but inc.next() hasn't been called yet.
// If the record exists, hasNext() will be true.
gs.print(inc.hasNext());
// Result: Print Boolean value (True) if there are any incidents.

Unique Identifiers: getUniqueValue() method

This method conveniently returns the `sys_id` of the current record, which is its unique identifier in ServiceNow, unless otherwise specified for specific tables.

Exercise 24: Gets the unique key of the record, which is usually the sys_id unless otherwise specified.

var inc = new GlideRecord('incident');
inc.query();
if (inc.next()) { // Move to the first record
    var uniqvalue = inc.getUniqueValue();
    gs.print(uniqvalue);
}
// Result: Print the sys_id of the first incident found.

CRUD Operations and Record Management

Beyond just reading, GlideRecord empowers you to create, update, and delete records, giving you full control over your ServiceNow data.

Setting Field Values: setValue() method

This method is used to programmatically set the value of a specific field on the current GlideRecord object. It's especially useful when field names are dynamic or when you prefer a more explicit way to set values.

Exercise 25: This method is used to sets the value of the specific field with the specified value.

var attriName = 'category';
var inc = new GlideRecord('incident');
inc.initialize(); // Prepares a new, empty incident record
inc.setValue(attriName, 'network'); // Set 'category' field to 'network'
inc.setValue('short_description', 'Critical VPN Issue'); // Set 'short_description' field
inc.insert(); // Save the new record to the database
gs.print('Category is ' + inc.category + ' and ' + 'issue is: ' + inc.short_description);
// Result: Create a new record and Set a value into category field, then print the values.

Getting Field Elements: getElement() method

The getElement() method returns a GlideElement object for the specified field. This object can be used to access properties and methods related to that specific field, like its display value, label, or whether it's read-only.

Exercise 26: This is used to get the specified column of the current record.

var elementName = 'short_description';
var inc = new GlideRecord('incident');
inc.initialize();
inc.setValue(elementName, 'I am facing VPN Problem');
inc.insert();
gs.print(inc.getElement('short_description')); // This will print the GlideElement object, which stringifies to the value
// Result: Print current record column value for short_description.

Getting the Record Class Name: getRecordClassName() method

This method retrieves the class name (which is typically the table name) for the current GlideRecord object.

Exercise 27: Retrieves the class name for the current record.

var inc = new GlideRecord('change_request');
var grcn = inc.getRecordClassName();
gs.info(grcn);
// Result: Print record class name (e.g., 'change_request').

Creating and Inserting Records: initialize() and insert() methods

The process for creating a new record is straightforward: initialize() sets up a blank record, you set its field values, and then insert() saves it to the database.

Exercise 28: These methods are used to Inserts a new record using the field values that have been set for the current record.

var inc = new GlideRecord('incident');
inc.initialize(); // Compose incident form (prepares a new, empty incident record)
inc.category = 'network'; // Set field values directly
inc.short_description = 'Firewall Issue';
inc.priority = 1; // Corrected typo from priorty
inc.insert(); // Create new record and save it to the database
gs.print(inc.number); // Print new record incident number
// Result: Create new record and print new record number (e.g., INC0010046).

Checking if a Record is New: isNewRecord() and newRecord() methods

newRecord() creates a new GlideRecord and assigns a unique ID, effectively preparing it for insertion. isNewRecord() checks if the current GlideRecord object represents a record that hasn't been saved to the database yet.

Exercise 29: Checks if the current record is a new record that has not yet been inserted into the database.

var inc = new GlideRecord('incident');
inc.newRecord(); // Creates a new GlideRecord instance ready for insertion
gs.info(inc.isNewRecord());
// Result: Return boolean value true or false (value is True).

Validating Table Existence: isValid() method

This method checks if the table specified when instantiating the GlideRecord object actually exists in the ServiceNow instance.

Exercise 30: Define the current table exist or not. If table exist display true not exist display false.

var inc = new GlideRecord('incident');
gs.print(inc.isValid());
// Result: True (as 'incident' is a standard table).

// Example 2: Non-existent table
var fakeGR = new GlideRecord('uday');
gs.print(fakeGR.isValid());
// Result: False.

Validating Field Existence: isValidField() method

This method checks if a specified field exists within the current GlideRecord's table definition.

Exercise 31: Determines if the specified field is defined in the current table. If Field exist in current record display true not exist display false.

var inc = new GlideRecord('incident');
gs.print(inc.isValidField('category'));
// Result: Boolean value is True (as 'category' is a standard field on incident).

Getting a Record Link: getLink() and getProperty() methods

getLink() retrieves the URL to the current record. Often combined with `gs.getProperty('glide.servlet.uri')` to get the base URL of your instance.

Exercise 32: Retrieves a link to the current record.

var inc = new GlideRecord('incident');
inc.addActiveQuery();
inc.addQuery('category', 'software');
inc.addQuery('priority', 1);
inc.query();
if (inc.next()) { // Get the first matching record
    gs.print(gs.getProperty('glide.servlet.uri') + inc.getLink(false));
}
// Result: Return the link of the first record found (e.g., "https://yourinstance.service-now.com/nav_to.do?uri=incident.do?sys_id=a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6").

Validating Record Existence After Query/Get: isValidRecord() method

This method determines if a record was actually returned by a `get()` operation or if the GlideRecord is currently pointing to a valid record after a `query()` and `next()` call.

Exercise 33: Determines if a record was actually returned by the query/get record operation.

var inc = new GlideRecord('incident');
inc.get('number', 'INC0010012'); // Try to retrieve a specific incident
gs.print(inc.number + ' exists: ' + inc.isValidRecord());
// Result: Display boolean value either true or false (True, if INC0010012 exists).

Creating a New Record (Alternative): newRecord() method

Similar to initialize(), `newRecord()` prepares a new GlideRecord for insertion, setting default values and assigning a unique ID.

Exercise 34: Creates a new GlideRecord record, sets the default values for the fields, and assigns a unique ID to the record.

var inc = new GlideRecord('incident');
inc.newRecord(); // Creates a new GlideRecord instance and sets default values
inc.short_description = 'Creating new record using newRecord()';
inc.category = 'software';
inc.insert();
gs.print(inc.number);
// Result: Create new record and print its incident number.

Finding Null Values: addNullQuery() method

This method allows you to filter records where the value of a specified field is null or empty.

Exercise 35: Display all records where the value of the specified field is null.

var inc = new GlideRecord('incident');
inc.addNullQuery('short_description'); // Find records where short_description is empty/null
inc.query();
while (inc.next()) {
    gs.print(inc.number);
}
// Result: Print all records where the specific field value is Null.

Finding Non-Null Values: addNotNullQuery() method

This is the opposite of addNullQuery(); it filters for records where the specified field has a value.

Exercise 36: Opposite of addNullQuery methods display all records where the value of the specified field is not null.

var inc = new GlideRecord('incident');
inc.addNotNullQuery('short_description'); // Find records where short_description is NOT empty/null
inc.query();
while (inc.next()) {
    gs.print(inc.number + ' - ' + inc.short_description);
}
// Result: Print all records where the specific field value is not null.

Updating Single Records: update() method

To modify an existing record, you first retrieve it, set the new values, and then call `update()` to save the changes.

Exercise 37: Update specific record from table

var inc = new GlideRecord('incident');
inc.get('number', 'INC0000057'); // Get the specific incident to update
if (inc.isValidRecord()) {
    inc.setValue('state', 2); // Set 'state' to 'In Progress' (assuming '2' is the value)
    inc.update();
    gs.print('Incident ' + inc.number + ' updated to state: ' + inc.state.getDisplayValue());
} else {
    gs.print('Incident INC0000057 not found for update.');
}
// Result: Update record as expected.

Updating Multiple Records: updateMultiple() method

This powerful method updates all records that match the current query conditions with the field values you've set on the GlideRecord object. Use with extreme caution!

Exercise 38: Updates multiple records in a stated query with a specified set of changes from respected table.

var inc = new GlideRecord('incident');
inc.addQuery('category', 'hardware'); // Query for all incidents with category 'hardware'
inc.setValue('category', 'software'); // Set their category to 'software'
inc.updateMultiple(); // Apply this change to ALL matching records
gs.print('All hardware incidents updated to software category.');
// Result: Update multiple records as expected.

// Exercise 2: Update all priority 3 incidents to priority 2
var inc2 = new GlideRecord('incident');
inc2.addQuery('priority', 3);
inc2.setValue('priority', 2);
inc2.updateMultiple();
gs.print('All priority 3 incidents updated to priority 2.');

Deleting Single Records: deleteRecord() method

This method permanently removes a single record from the database. Make sure you retrieve the correct record first.

Exercise 39: This method is used to delete single record from table.

var inc = new GlideRecord('incident');
inc.get('number', 'INC0010013'); // Get the specific record to delete
if (inc.isValidRecord()) {
    inc.deleteRecord();
    gs.print('Incident ' + inc.number + ' deleted.');
} else {
    gs.print('Incident INC0010013 not found for deletion.');
}
// Result: Delete single record as expected.

Deleting Multiple Records: deleteMultiple() method

This is the most dangerous GlideRecord operation. It deletes *all* records that satisfy the current query condition. Always double-check your query!

Exercise 40: Deletes multiple records that satisfy the query condition.

var inc = new GlideRecord('incident');
inc.addQuery('priority', 4); // Query for all incidents with priority 4
inc.query(); // Execute the query
var deletedCount = inc.getRowCount(); // Get the count before deleting
inc.deleteMultiple(); // Delete all matching records
gs.print(deletedCount + ' incidents with priority 4 deleted.');
// Result: Delete multiple records as expected.

Access Control Checks: canCreate(), canRead(), canWrite(), canDelete() methods

These methods are invaluable for scripts that need to respect ServiceNow's Access Control Lists (ACLs). They tell you if the currently logged-in user (or system user if running in a business rule) has permission to perform an action on the record.

Exercise 41: Determines if the Access Control Rules, which include the user's roles, permit creating new records in this table.

var inc = new GlideRecord('incident');
gs.print('Can create incident records? ' + inc.canCreate());
// Result: True (user has permission to create incident record, assuming appropriate roles like itil).

Exercise 42: Determines if the Access Control Rules, which include the user's roles, permit reading records in this table.

var inc = new GlideRecord('incident');
gs.print('Can read incident records? ' + inc.canRead());
// Result: True (user has permission to read incident record).

Exercise 43: Determines if the Access Control Rules, which include the user's roles, permit editing records in this table.

var inc = new GlideRecord('incident');
gs.print('Can write to incident records? ' + inc.canWrite());
// Result: True (user has permission to write incident record).

Exercise 44: Determines if the Access Control Rules, which include the user's roles, permit deleting records in this table.

var inc = new GlideRecord('incident');
gs.print('Can delete incident records? ' + inc.canDelete());
// Result: True (user has permission to delete incident record).

Controlling System Fields and Workflows: autoSysFields() and setWorkflow() methods

These are advanced methods, often used in integrations or data imports, where you want to bypass standard system behaviors.

• autoSysFields(false): Prevents system fields like `sys_updated_on`, `sys_updated_by`, `sys_mod_count`, `sys_created_on`, `sys_created_by` from being automatically updated when you call `update()`. This is useful for preserving historical data during migrations or specific integrations. (Note: This might not work in Scoped Applications).
• setWorkflow(false): Prevents Business Rules, Workflow Activities, and other engine-driven automation from running when `update()` or `insert()` is called. Use with extreme caution, as it bypasses critical business logic!

Exercise 45: Update multiple records without update any system fields

var inc = new GlideRecord('incident');
inc.addQuery('state', 1); // Find incidents in 'New' state (value '1')
inc.query();

while (inc.next()) {
    inc.autoSysFields(false); // Do not update system fields (updated_by, updated_on, etc.)
    inc.setWorkflow(false); // Do not run business rules, workflows
    inc.setValue('state', 2); // Change state to 'In Progress' (value '2')
    inc.update();
}
gs.print('Incidents in state "New" updated to "In Progress" without system field or workflow updates.');
// Result: Updating records without update system fields.

Joining the Dots: addJoinQuery() method

`addJoinQuery()` allows you to query records from one table based on conditions in a related table. It performs an inner join, returning records only when there's a match in both tables.

Exercise 46: Find problems that have an incident attached. This example returns problems that have associated incidents.

var prob = new GlideRecord('problem');
// Find problems where the 'opened_by' user in the problem table
// is also the 'caller_id' of an associated incident.
prob.addJoinQuery('incident', 'opened_by', 'caller_id');
prob.query();

while (prob.next()) {
    gs.print('Problem with associated incident: ' + prob.number);
}
// Result: Display all problem records associated with an incident through the specified user relationship.

Building Robust Logic: getGlideObject(), getNumericValue() and setAbortAction() methods

setAbortAction(true) is often used in server-side scripts (like Business Rules) to stop the current database operation (insert, update, delete) if a validation check fails. This prevents invalid data from being saved.

Exercise 47: This is method is used to cancel current action when condition is false.

This script typically runs as a before insert/update Business Rule on a custom table (e.g., u_my_table) with two custom date fields: u_date1 and u_date2.

if ((!current.u_date1.nil()) && (!current.u_date2.nil())) { // Check if both dates are populated
    // Get GlideDateTime objects and then their numeric values for comparison
    var start = current.u_date1.getGlideObject().getNumericValue();
    var end = current.u_date2.getGlideObject().getNumericValue();

    if (start > end) { // If start date is after end date
        gs.addInfoMessage('Start date must be before end date.'); // Inform the user
        current.u_date1.setError('start must be before end'); // Highlight the problematic field on the form
        current.setAbortAction(true); // Prevent the record from being saved
    }
}
// Result: If an attempt is made to save a record where u_date1 is after u_date2,
// an info message appears, the u_date1 field gets an error, and the save operation is cancelled.

Troubleshooting Common GlideRecord Issues

Even seasoned developers run into snags. Here are some common GlideRecord issues and how to tackle them:

• No Records Returned:
  • Check your query conditions: Are they too restrictive? Are field names spelled correctly? (e.g., addQuery('short_descriptoin', '...') instead of short_description).
  • Data mismatch: Are you querying for priority = '1' when the field stores 1 - Critical or vice-versa? Use getDisplayValue() for display, but often getValue() for actual querying.
  • Table name: Is new GlideRecord('incident') correct, or should it be a different table? Use isValid() to check.
• Infinite Loop:
  • Forgetting inc.next() inside your while loop is a classic. The loop condition will always be true, and your script will hang.
• Performance Problems:
  • Large datasets: Are you querying for millions of records? Use setLimit() or add more specific addQuery() conditions to narrow down your results.
  • Unindexed fields: Queries on unindexed fields can be slow. Check field definitions.
  • gs.print()/gs.info() inside loops: Excessive logging inside a loop processing many records can slow things down. Remove or limit these for production scripts.
• Permissions Denied (Operations Fail):
  • If insert(), update(), or delete() fails, it's often an Access Control List (ACL) issue. The user (or system context) running the script doesn't have the necessary roles or conditions met. Use canCreate(), canWrite(), etc., to debug.
• Unintended Data Changes:
  • This usually stems from an incorrect query for updateMultiple() or deleteMultiple(). Always verify your addQuery() conditions thoroughly before running these bulk operations.

Interview Questions You Might Face

GlideRecord is fundamental, so expect questions about it during ServiceNow developer interviews. Here are some common ones:

• What's the difference between addQuery() and addEncodedQuery()? When would you use each? (Hint: Flexibility for simple AND vs. Complexity/UI-generated queries, including OR conditions)
• Explain getValue() vs. getDisplayValue(). (Hint: Stored internal value vs. human-readable label)
• How do you create a new record using GlideRecord? What methods are involved? (Hint: initialize() or newRecord(), setting values, insert())
• When would you use setWorkflow(false) or autoSysFields(false)? What are the implications? (Hint: Integrations/migrations, bypassing business rules/audit logs, use with extreme caution!)
• Why is inc.next() crucial in a GlideRecord query loop? (Hint: Iteration, fetching next record, preventing infinite loops)
• How would you ensure your GlideRecord script performs well on large tables? (Hint: Effective addQuery() conditions, setLimit(), `orderBy()` on indexed fields, avoid `getRowCount()` on huge queries if only iterating)
• How do you ensure a record exists before attempting to update or delete it? (Hint: isValidRecord() after get() or next())