servicenow The selected Shared List does not match the existing Authority Document list. Select a different Shared List or update the existing Shared List.

Swapnil Shirsik
Giga Guru

servicenow The selected Shared List does not match the existing Authority Document list. Select a different Shared List or update the existing Shared List.

The list is shared in UCF as mentioned in ServiceNow documentation, glide.attachment.extensions property contains json.

Please can anyone help to understand what needs to be done to resolve his error?

There is similar question-https://community.servicenow.com/community?id=community_question&sys_id=f1c4cd06dbfc5f002b6dfb651f9619f3

 

Does it mean that we need to create one shared list on UCF that contains all the authority documents that we previously importe and need to import now and then after importing to ServiceNow need to remove the unwanted old ones?

3 REPLIES 3

Anushree Randad
ServiceNow Employee
ServiceNow Employee

Hi Swapnil,

Yes, this is the current behavior. If you are importing a shared list from CCH, you need to add previously downloaded authority documents in it along with newly added documents.

Here is the documentation on it: 

https://docs.servicenow.com/bundle/sandiego-governance-risk-compliance/page/product/grc-ucf-import/task/download-a-shared-list.html

We are working on a solution which will remove this dependency and would allow you to import multiple shared lists as well as import documents without adding previously downloaded documents. It is on the roadmap for next year.

 

Thanks,

Anushree Randad

Principal Product Manager

ServiceNow

Archana36
Tera Contributor

Hi @Anushree Randad ,

 

Please advise if there is any workaround if the original list is not available.

 

Mohammed Kemal
Tera Guru

Hey @Anushree Randad ,

We are facing a significant roadblock in our efforts to import the shared list from UCF to ServiceNow using the API key. This is our first attempt, and the absence of previously downloaded authority document is preventing us from moving forward. We kindly request a timeline for a workaround or permanent fix to minimize the impact on our ongoing GRC implementation.

 Screenshot 2024-12-10 at 12.16.47 PM.png

Thanks,

Mohammed.