Project Workspace Home - Can't display the list - ACL failed error

Alpa82
Tera Expert

Hello experts, 
We have enabled the new project workspace and the users with PM role can view the projects in the grid view (cards) but when switching to the list view, the bellow message is displayed.

'Can't display this list. ACL failed for data_broker with no defined failure result'

This issue does not appear for admin. Could you please advise what is the cause?

Alpa82_0-1730661744389.png
As well the search field does not seem to react for non-admin user (after entering the search term, it basically does not react).

Thank you

 

 

1 ACCEPTED SOLUTION

PaulaaO
Mega Sage

Hiya, we came across the same when we upgraded and updated the plugin. This is a bug confirmed by ServiceNow Support and it has to do with 2 ACLs, of type = ux_data_broker and operation = execute and these are:

e364ad62ff100210397cffffffffffa3

ab3c8a52ff500210397cffffffffff20

 

OOTB my understanding is that both ACLs should have snc_internal and snc_external. In our case we only had snc_external which is why we had the same issue as raised on this post.

 

The tricky part is that for us, both these ACLs are part of "now-list-commons" application which is ReadOnly so we cannot amend these ACLs as a client (not even with elevated admin role).

 

My suggestion in terms of next steps:

- try to repair the plugin sn_pw to see if the behaviour is corrected

- if it isn't see if these ACLs are editable for you to add both those roles mentioned above

- if you cannot do the changes, raise a case with SN Support but a piece of advice - ask them to apply these changes in an update set created on that application from the start so you can move the changes between environments (it's my current blocker now as they changed it in Default and cannot create an update set and move the changes into it due to the restriction at the application level)

 

Hope this helps, good luck 🙂

View solution in original post

20 REPLIES 20

vmozuna
Tera Contributor

Did you get this figured out - we are seeing the same issue. 

PaulaaO
Mega Sage

Hiya, we came across the same when we upgraded and updated the plugin. This is a bug confirmed by ServiceNow Support and it has to do with 2 ACLs, of type = ux_data_broker and operation = execute and these are:

e364ad62ff100210397cffffffffffa3

ab3c8a52ff500210397cffffffffff20

 

OOTB my understanding is that both ACLs should have snc_internal and snc_external. In our case we only had snc_external which is why we had the same issue as raised on this post.

 

The tricky part is that for us, both these ACLs are part of "now-list-commons" application which is ReadOnly so we cannot amend these ACLs as a client (not even with elevated admin role).

 

My suggestion in terms of next steps:

- try to repair the plugin sn_pw to see if the behaviour is corrected

- if it isn't see if these ACLs are editable for you to add both those roles mentioned above

- if you cannot do the changes, raise a case with SN Support but a piece of advice - ask them to apply these changes in an update set created on that application from the start so you can move the changes between environments (it's my current blocker now as they changed it in Default and cannot create an update set and move the changes into it due to the restriction at the application level)

 

Hope this helps, good luck 🙂

Hi @PaulaaO ,

You said this is a bug confirmed by ServiceNow Support. Dou you have a reference for the KB article?

Thanks

@jose_quinonez I have the PRB -> PRB1804211 I haven't checked whether there is a KB article, but in terms of an update, I raised another case with them and they provided me with the XMLs of the ACL roles.

So I guess that as another workaround is to import the OOTB acl roles and that should sort the matter ( I have done it and it worked, you need to elevate your role but that's enough). I have been told this is being fixed in Yokohama