Discrepancy Between GlideRecord.getRowCount() and Actual Table Count in cmdb_sam_sw_install

[jeevanjadhav]

Hi Everyone,

I'm encountering a discrepancy between the number of records retrieved using a background script and the actual count shown in the cmdb_sam_sw_install table UI.

Here’s the script I’m running:

var installGR = new GlideRecord('cmdb_sam_sw_install');

installGR.query();

gs.info('Matching Software Installs Count: ' + installGR.getRowCount());

This script outputs:

Script: Matching Software Installs Count: - 427991

However, when I check the same table in the UI (with all filters cleared), the total number of records displayed is 410,910.

I’d like to understand:

• Why is getRowCount() returning more records than what I see in the table UI?
• Could this be due to ACLs, replication lag, or some other issue?
• What’s the best way to ensure the script returns a count that matches what users see in the UI?

[Di Zhang]

It was effected by ACL.  if you need to get results same as UI, you should use GildeQuery

[Ankur Bawiskar]

@jeevanjadhav 

GlideRecord won't consider ACL.

Check any Table level READ ACL or Query business rule is restricting records.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@jeevanjadhav 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Pranesh072]

You can use GlideRecordSecure which enforce ACLs. Most probably there can be query BR which is restricting the records.