Knowledge Base Problems in Update set

[AyushKumarM]

I’m migrating a Knowledge Base and its associated Knowledge Articles using an update set. I have created application files for both the Knowledge Base and the Knowledge Articles, and they are correctly showing in the update set. Additionally, the Knowledge Articles maintain the correct reference to their respective Knowledge Base.

However, I’ve encountered an issue with the contributor permissions. The records that define who can contribute and who cannot contribute are present in the update set, but they are missing the reference to the Knowledge Base field.

As a result, when the update set is previewed or committed, these permission records are not associated with any Knowledge Base, which breaks the expected access configuration.

Has anyone experienced this issue before?

[TryciaK]

Yes, this is a known issue that can occur when migrating Knowledge Base configurations using update sets in ServiceNow. While the update set may capture the Knowledge Base and its associated articles correctly—including their relationships—the contributor permission records (typically from the kb_knowledge_contributor or related tables) may not retain their reference to the Knowledge Base field during the export.

[AyushKumarM]

Hey @TryciaK , thanks for replying. Is there any open ticket regarding this or workaround known to you?

[AbinC]

HI,

you can always change the Knowledge Base and Category in the form for a knowledge article provided you have write access to the Knowledge Base you are trying to change to. 

Once you change the Knowledge Base, the article will follow the workflow configured for that new Knowledge Base for publishing. 

One thing to remember is that if you are using Knowledge Blocks then they will not work in the new Knowledge Base and you may need to either move the blocks or remove them. Knowledge Blocks are limited to a knowledge base thing. 

Hope this helps. Pls mark helpful if it does. 

Thanks,

Abin.