<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question How to detect query_range ACL errors using ATF? in Developer forum</title>
    <link>https://www.servicenow.com/community/developer-forum/how-to-detect-query-range-acl-errors-using-atf/m-p/3509493#M1250765</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m currently trying to detect query_range ACL issues using ATF.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I observed:&lt;BR /&gt;- When using a non-admin user in the list view and applying certain filters (e.g. contains / LIKE), a query_range warning appears in the UI.&lt;BR /&gt;- However, when I try to simulate similar queries server-side using GlideRecord (e.g. addEncodedQuery), everything executes without errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it seems like:&lt;BR /&gt;- The UI detects a restriction (query_range warning)&lt;BR /&gt;- Server-side scripts do not reflect this behavior&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My questions:&lt;BR /&gt;- Is query_range only enforced or detectable in the list UI context?&lt;BR /&gt;- Is there any way to detect these restrictions server-side?&lt;BR /&gt;- How would you typically test this in ATF?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 17 Mar 2026 13:56:50 GMT</pubDate>
    <dc:creator>Sn_devT</dc:creator>
    <dc:date>2026-03-17T13:56:50Z</dc:date>
    <item>
      <title>How to detect query_range ACL errors using ATF?</title>
      <link>https://www.servicenow.com/community/developer-forum/how-to-detect-query-range-acl-errors-using-atf/m-p/3509493#M1250765</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I’m currently trying to detect query_range ACL issues using ATF.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I observed:&lt;BR /&gt;- When using a non-admin user in the list view and applying certain filters (e.g. contains / LIKE), a query_range warning appears in the UI.&lt;BR /&gt;- However, when I try to simulate similar queries server-side using GlideRecord (e.g. addEncodedQuery), everything executes without errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So it seems like:&lt;BR /&gt;- The UI detects a restriction (query_range warning)&lt;BR /&gt;- Server-side scripts do not reflect this behavior&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My questions:&lt;BR /&gt;- Is query_range only enforced or detectable in the list UI context?&lt;BR /&gt;- Is there any way to detect these restrictions server-side?&lt;BR /&gt;- How would you typically test this in ATF?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2026 13:56:50 GMT</pubDate>
      <guid>https://www.servicenow.com/community/developer-forum/how-to-detect-query-range-acl-errors-using-atf/m-p/3509493#M1250765</guid>
      <dc:creator>Sn_devT</dc:creator>
      <dc:date>2026-03-17T13:56:50Z</dc:date>
    </item>
  </channel>
</rss>

