How to move KB articles from one instance to other instance through script with attachments?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2017 06:52 PM
Hi All,
Can any one please help me on the below task.
How to move KB articles from one instance to other instance through script with attachments?
Is it possible, any one know please guide me on that.
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-15-2024 07:23 PM
Technically it's possible. It's not just attachments, data from other tables can also be captured manually in update sets. Btw configurations are also just tables with data. You can give it a try.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-17-2025 08:50 AM
what about references within KBA#1111 to KBA#2222? In the new instance the KBA2 will have different reference url (incl. different sys_id). Also KBA#2222 probably will have different number in the new system or it will keep the same number ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2025 06:18 PM
@KirilD Since the records are captured via updateset, their 'sys_id' won't change after deploying to target instance. Hence, to answer your question, 'sys_id' and 'number' of KB articles won't change in target instance. Hope this answers your query.
Hit "Correct", "Helpful" or "Like" depending on the impact of the response.
Regards,
Kamal S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-12-2025 04:09 AM
I am getting error while committing update set in target instance can you please help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2025 06:13 PM
@Ramakrishna Rao You need to deploy missing records in the tables "kb_knowledge_summary" and "kb_version" to resolve this error.
1. Open the error message to see the sys_id of the records which are missing in the target instance.
2. From the source instance do an XML export of those particular missing records and import them into target instance in respective tables.
3. Preview the updateset again. You'll notice the error caused due to missing records will no longer appear.
Hit "Correct", "Helpful" or "Like" depending on the impact of the response.
Regards,
Kamal S