Record not visible

[Priyanka_Ghosh]

Hello,

I can access the record with direct URL but not using list view. What can be the probable cause?

Is it something around Query BR or ACLs? If yes, could anyone please explain how?

-Thanks

[Dr Atul G- LNG]

Hi @Priyanka_Ghosh 

Look like it can be acl.issues.

[Priyanka_Ghosh]

Hello,

Could you please explain how ACL would be causing this issue? as the record isn't visible in list view but it's visible when accessed through URL

[Dr Atul G- LNG]

Hi @Priyanka_Ghosh 

https://www.servicenow.com/community/architect-forum/i-can-see-a-record-in-the-list-view-but-when-i-...

[John Dahl]

Considering your explanation, I suspect something else is at play, not an ACL and not a Query Business Rule.

When you query a table, the query business rules run first and they modify the query that is run against the database. That may prevent the record from being returned from the database so there are no messages displayed in the list view. It's as if the record simply did not exist. This should also prevent you from accessing the record directly by URL.. you would get a "Record not found" error.

Once the data is returned from the database, then each record is compared to the ACLs that apply. For any records that are blocked by ACL, you will see the security constraint message in the list view. This is because the restriction is taking place in the application after the database activity is complete. It's like someone saying "Yes, that record does exist, but you don't get to see it"

There is also a third option, using Data Filtration. This may also prevent you from accessing a record, but I  do not recall if it provides any notification of removed records. I would look here. You can enable Session debugging to help narrow down what actions are in play and which may be affecting the record you are trying to access.