Question 1

What causes GlideAggregate Returning Wrong Count in ServiceNow?

Accepted Answer

ACL context mismatch between queries — Check if your aggregate runs as admin while comparison query runs as end user. Look at the sys_user session in System Logs > Session Debug and compare the user context between your GlideAggregate and GlideRecord calls. Null values excluded from groupBy operation — Examine your groupBy field in the target table's list view and filter for empty values. GlideAggregate automatically excludes null/empty groupBy values while GlideRecord includes records with null values in the count. Domain separation filtering inconsistency — Check the Domain field on your target table and verify domain scoping in System Definition > Domains. Business rules may run in global domain while list views respect user's domain restrictions. Missing query conditions in aggregate — Compare your GlideAggregate addQuery() calls with the list view filters or GlideRecord query. Check for missing encoded queries, date ranges, or state filters that exist in your comparison query. Table inheritance causing record inclusion mismatch — Check if your table extends another table in System Definition > Tables. Look for records in child tables that may be included in aggregate but filtered out in list view due to table-specific ACLs.

Question 2

How do you fix GlideAggregate Returning Wrong Count in ServiceNow?

Accepted Answer

How to fix it First, verify the user context by adding gs.log('User: ' + gs.getUserName() + ', Admin: ' + gs.hasRole('admin')) before both your GlideAggregate and comparison queries. Check System Logs > System Log > All to see if the user context differs between queries. If yes, force the same context using gs.getSession().impersonate('username') before your aggregate. Identify null value issues by running a GlideRecord query with addNullQuery('your_groupby_field') to count records with empty groupBy fields. If null values are the issue, either remove the groupBy clause or add addNotNullQuery('your_groupby_field') to both queries for consistency. For domain issues, check current domain with gs.getSession().getCurrentDomainID() and set to global domain using gs.getSession().setDomainID('global') before the aggregate if needed. Debug query differences by logging both encoded queries: add gs.log('Aggregate query: ' + ga.getEncodedQuery()) and gs.log('Record query: ' + gr.getEncodedQuery()). Copy the encoded query from your aggregate and paste it into the list view filter to verify the same records are returned visually. For table inheritance issues, check the sys_class_name field and add addQuery('sys_class_name', 'table_name') to both queries if you need to restrict to specific table types.

Question 3

How do you prevent GlideAggregate Returning Wrong Count in ServiceNow?

Accepted Answer

Always wrap GlideAggregate queries in the same user context as your comparison queries using gs.getSession().impersonate() or proper role checks. Log both encoded queries during development to ensure filter parity between GlideAggregate and GlideRecord comparisons. When using groupBy, explicitly handle null values by adding addNotNullQuery() to both aggregate and comparison queries. Set up consistent domain context by checking getCurrentDomainID() before running aggregates in business rules that span multiple domains. Create unit tests that compare GlideAggregate results with GlideRecord counts using identical query conditions to catch discrepancies early.

GlideAggregate Returning Wrong Count in ServiceNow

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge

Related Articles