System Properties

glide.db.max_view_records

The system property glide.db.max_view_records controls the maximum number of rows returned.

Specify the number of records to return for a database view when the view is used in a script.

A property called glide.db.max_view_records controls the maximum number of rows returned when running a GlideRecord query in a script. The default value for this property is 10000. To change this value, add the property to the System Property (sys_properties) table and edit the number of rows to return.

Source: Configuring the number of records to return

If this threshold is breached this will be logged as

08.04.2024 16:50:21 Warning 2024-04-08 16:50:21.708 - The current rowCount of 10001 is greater than the value set as system property 'glide.db.max_view_records': 10000. Records could be missing. Please check the amount of records you are expecting.

08.04.2024 16:50:21 Warning 2024-04-08 16:50:21.708 - The current rowCount of 10001 is greater than the value set as system property 'glide.db.max_view_records': 10000. Records could be missing. Please check the amount of records you are expecting.

and the returned JSON will include a warning

{
  "metadata": {
    ...,
    "row_count": 10001,
    "warnings": [
      "The current rowCount of 10001 is greater than the value set as system property 'glide.db.max_view_records': 10000. Records could be missing. Please check the amount of records you are expecting."
    ]
  },
  ...
}

If you see these warnings, please consider increasing the glide.db.max_view_records value or restricting your queries.

Squid intentionally does not sort or page data. What entities are returned if this threshold is breached is totally arbitrary.

Why no paging!?

Squid attempts to deliver as reliable and reproducible data as possible. Data in dynamic systems like ServiceNow is a moving target. Pagination implies that data is returned at different points in time and as pagination would only come into play with large data amounts every request/response cycle would take several minutes. As Squid is stateless, we would need to reexecute the query against the then current state of data.

Added data in a previous page? Get redundant data in the current page.

Removed data in a previous page? Data is missing in the current page.

Hey, Squid, you're inconsistent! As that is something we definitely do not want to do here, we do not support pagination.

x_a46gh_squidx.useScopedCache

The system property x_a46gh_squidx.useScopedCache controls whether Squid uses scoped caches or not.

Scoped caches store reference configurations and view metadata between requests, reducing execution time by ~100ms per request and lowering database load. Squid is installed with this system property set to true.

See Scoped Caches for details on what is cached and how to verify caching is working.

x_a46gh_squidx.allowAclOverride

Controls whether Squid bypasses ServiceNow ACLs for predefined configurations.

Value	Behavior	Recommended
false (default)	ACLs enforced	No
true	ACLs bypassed	Yes

Support requirement

arc46 cannot provide support unless this property is set to true.

Why bypass ACLs? When ACLs deny access, ServiceNow silently omits records — no error, no warning, just missing data. For mission-critical integrations, this is dangerous.

See ServiceNow ACLs and Squid for the full explanation of this security design decision.