ACL error after upgrade

[JohnnySnow]

Hi Team,

We have a custom application with a table say ABC. This table is extended from task table. We recently upgraded from Vancouver to Washington (and the issue seems to happen post this). When the user is trying to open "Assigned to" the user receives this below error

Upon analyzing I can see that below ACLs are causing this issue

and user doesn't have any of the above roles.

I'm trying to understand if something has changed in terms of role in Washington release, why the issue didnt come up in Vancouver instance.

I'm assuming to resolve we can add the custom table role in one of the above ACL.

Is there any other way to fix and analyze why the issue came up after upgrade?

[Dnyaneshwaree]

Hello @JohnnySnow,

Check/ compare the ACLs that are for assigned to field or your custom table from before and after upgrade. Or check any impact of upgrade on that ACLs. 

[JohnnySnow]

Thanks for the reply, I did check but couldn't find any changes.

[JohnnySnow]

Does any one have similar issues?

[Dnyaneshwaree]

Check this:

https://www.servicenow.com/community/csm-forum/error-on-the-incident-form/m-p/3001818
https://www.servicenow.com/community/csm-forum/getting-an-error-while-looking-up-any-incident-ticket...