GlideAggregate COUNT in ServiceNow — How to Count Records Correctly

Counting records in ServiceNow correctly requires understanding GlideAggregate. Using GlideRecord to count records works but is significantly less efficient — GlideRecord loads every matching record into memory before counting. GlideAggregate pushes the COUNT operation to the database and returns only the number.

Basic COUNT

// Count all active incidents
var ga = new GlideAggregate('incident');
ga.addAggregate('COUNT');
ga.addEncodedQuery('active=true');
ga.query();
ga.next();
var count = ga.getAggregate('COUNT');
gs.log('Active incidents: ' + count);
// Output: "Active incidents: 247"

COUNT with groupBy — Counts Per Group

The most useful pattern — count records broken down by a field value:

// Count incidents grouped by priority
var ga = new GlideAggregate('incident');
ga.addAggregate('COUNT');
ga.addEncodedQuery('active=true');
ga.groupBy('priority');
ga.orderBy('priority');
ga.query();

while (ga.next()) {
    var priority = ga.getDisplayValue('priority');
    var count = ga.getAggregate('COUNT');
    gs.log(priority + ': ' + count);
}
// Output:
// "1 - Critical: 3"
// "2 - High: 12"
// "3 - Moderate: 48"

COUNT on a Specific Field

You can count a specific field rather than all rows. This is useful for counting non-null values:

// Count incidents where assigned_to is populated
var ga = new GlideAggregate('incident');
ga.addAggregate('COUNT', 'assigned_to');
ga.addEncodedQuery('active=true');
ga.query();
ga.next();
var assignedCount = ga.getAggregate('COUNT', 'assigned_to');
gs.log('Assigned incidents: ' + assignedCount);

COUNT DISTINCT — Unique Values

// Count how many unique assignment groups have active incidents
var ga = new GlideAggregate('incident');
ga.addAggregate('COUNT DISTINCT', 'assignment_group');
ga.addEncodedQuery('active=true');
ga.query();
ga.next();
var uniqueGroups = ga.getAggregate('COUNT DISTINCT', 'assignment_group');
gs.log('Groups with active incidents: ' + uniqueGroups);

Multiple Aggregates in One Query

// Get count, min, and max in a single database call
var ga = new GlideAggregate('incident');
ga.addAggregate('COUNT');
ga.addAggregate('MIN', 'sys_created_on');
ga.addAggregate('MAX', 'sys_created_on');
ga.addEncodedQuery('active=true^priority=1');
ga.query();

if (ga.next()) {
    gs.log('Count: ' + ga.getAggregate('COUNT'));
    gs.log('Oldest: ' + ga.getAggregate('MIN', 'sys_created_on'));
    gs.log('Newest: ' + ga.getAggregate('MAX', 'sys_created_on'));
}

GlideAggregate vs GlideRecord for Counting

Method	How it works	Performance
GlideAggregate COUNT	Database-level COUNT(*)	Extremely fast — one DB call
GlideRecord + getRowCount()	Loads all matching records	Slow on large tables
GlideRecord loop counter	Iterates every record	Slowest — avoid entirely

On a table with 100,000 records, GlideAggregate COUNT returns in milliseconds. GlideRecord getRowCount() may take several seconds.

Using GlideAggregate in a Script Include

// Reusable function to get record count
function getRecordCount(table, encodedQuery) {
    var ga = new GlideAggregate(table);
    ga.addAggregate('COUNT');
    if (encodedQuery) {
        ga.addEncodedQuery(encodedQuery);
    }
    ga.query();
    if (ga.next()) {
        return parseInt(ga.getAggregate('COUNT'));
    }
    return 0;
}

// Usage
var p1Count = getRecordCount('incident', 'active=true^priority=1');
gs.log('P1 count: ' + p1Count);

Common Mistake — Calling getAggregate Before next()

// ❌ Wrong — getAggregate called before next()
var ga = new GlideAggregate('incident');
ga.addAggregate('COUNT');
ga.query();
var count = ga.getAggregate('COUNT'); // Returns null

// ✅ Correct — always call next() first
var ga = new GlideAggregate('incident');
ga.addAggregate('COUNT');
ga.query();
ga.next(); // Must call this before getAggregate
var count = ga.getAggregate('COUNT'); // Returns the count

COUNT DISTINCT — counting unique values

COUNT DISTINCT is particularly useful for metrics like unique users, unique assets affected, or distinct categories without duplicates inflating the count.

SUM — totalling numeric fields

AVG — calculating averages

MIN and MAX

Multiple aggregates in one query

You can request multiple aggregate functions in a single GlideAggregate query — avoiding multiple round trips to the database:

Using GlideAggregate in Script Includes for dashboards

GlideAggregate is the engine behind most Performance Analytics indicators and custom dashboards. Wrapping aggregate queries in a Script Include keeps the logic reusable and testable:

GlideAggregate vs GlideRecord counting — the performance case

The performance difference between GlideAggregate and counting with a GlideRecord loop is not academic — it is the difference between a query that returns in milliseconds and one that loads thousands of objects into memory. GlideRecord loads the full record object for every row it retrieves. GlideAggregate pushes the COUNT to the database engine and returns a single number. With RaptorDB's columnar index, GlideAggregate operations are even faster on large tables because the column-store is specifically optimised for aggregation queries.

The Instance Scan "GlideRecord count" finding specifically catches the pattern of using a GlideRecord loop to count records. If you see that finding in your instance, replacing every occurrence with GlideAggregate is one of the highest-ROI performance fixes available.

Ordering aggregate results

Combining GlideAggregate with a Script Include for a Gauge widget

Handling null results safely

When GlideAggregate is not the right tool

GlideAggregate is for aggregating data across multiple records. For checking existence (does at least one record match this condition?), a GlideRecord with setLimit(1) is simpler and equally performant. For fetching individual record fields, GlideRecord is correct. GlideAggregate shines specifically for COUNT, SUM, AVG, MIN, MAX operations across record sets — the operations that would otherwise require loading every record into memory.

Using GlideAggregate in Scheduled Jobs

GlideAggregate combined with Scheduled Jobs is the standard pattern for generating daily summary metrics. The job runs at a set time, executes aggregate queries across multiple tables, and writes results to a custom reporting table or triggers a notification. This pattern scales to any data volume because it never loads records into memory — only the aggregated numbers travel up the call stack.

GlideAggregate in technical interviews

GlideAggregate appears in almost every mid-level ServiceNow technical interview. The typical question: "How would you count active P1 incidents without loading every record into memory?" The expected answer describes GlideAggregate, addAggregate('COUNT'), query(), next(), and getAggregate(). The follow-up that separates strong candidates: explaining that GlideRecord iterates application-side while GlideAggregate pushes the COUNT to the database engine — the same distinction that drives the performance difference. Combine this with knowledge of RaptorDB's columnar index optimising aggregate queries, and you demonstrate architectural understanding beyond syntax familiarity.

Combining GlideAggregate with gs utility methods

GlideAggregate queries often need time-bound filters. The gs utility methods provide the date boundaries — gs.beginningOfThisMonth(), gs.daysAgo(7), gs.endOfToday() — which combine naturally with GlideAggregate encoded query syntax to produce metrics for specific time windows:

This pattern — GlideAggregate + gs date methods + groupBy + a Script Include wrapper — is the standard building block for operational dashboards, weekly digest emails, and Performance Analytics custom indicators. Learn it once and apply it across every metrics use case you encounter.

GlideAggregate COUNT in ServiceNow — How to Count Records Correctly

Basic COUNT

COUNT with groupBy — Counts Per Group

COUNT on a Specific Field

COUNT DISTINCT — Unique Values

Multiple Aggregates in One Query

GlideAggregate vs GlideRecord for Counting

Using GlideAggregate in a Script Include

Common Mistake — Calling getAggregate Before next()

COUNT DISTINCT — counting unique values

SUM — totalling numeric fields

AVG — calculating averages

MIN and MAX

Multiple aggregates in one query

Using GlideAggregate in Script Includes for dashboards

GlideAggregate vs GlideRecord counting — the performance case

Ordering aggregate results

Combining GlideAggregate with a Script Include for a Gauge widget

Handling null results safely

When GlideAggregate is not the right tool

Using GlideAggregate in Scheduled Jobs

GlideAggregate in technical interviews

Combining GlideAggregate with gs utility methods

Want the complete reference?

One practical ServiceNow tip every week.