Skipped Records are ACL

Prateek Tyagi · ‎09-04-2022

Hi All,

I have upgrade the instance to san diego patch 7 .I have 12 skipped records . which are ACLs . Now when i Compare them with the base system they have a difference in the operation field of the ACL . In base system the operation field have the sys_id but in he customized one it is having the report_view . The sys_id is same when compared to the report_view record But in base it is having sys_id and in the customized one the name of that record. Can any one Explain ?

Thanks

Mark Manders · ‎09-04-2022

Not sure why it's showing up, because nothing really changed. I would just move them back to OOB, so they won't show up next time. I've had some of these in the past an logged a ticket with NowSupport asking them for the reason of this, but never got a useful answer.

If my answer helped you in any way, please then mark it as helpful. If it resolved the issue, please mark it as correct. This way others will find it in the solved queue and helps them on similar queries.

Mark

Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

View solution in original post

Ashok Kumar07 · ‎11-07-2022

Hi Mukesh

Any Solution Proposed for This Issue .Am facing the same issue in Tokyo Upgrade

Thanks.

Community Alums · ‎11-08-2022

We just went through them and reviewed them.

We raised this with ServiceNow via HI today.

Not sure if this is the answer - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1121670&source=Email&rank=2

Community Alums · ‎11-08-2022

got this from support - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1184514

Harish Kota · ‎11-14-2022

HI @Community Alums

You can safely ignore the skipped ACL's and mark them as reviewed as needed.
No changes or modifications have been made; the logs are reporting these RVAs as skipped due to customization.
No further action besides indicating the logs have been reviewed is required.