Translated KB articles always show Parent version 1.0 regardless of version used for translation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2025 02:34 PM
Why Translated KB articles always show Parent version 1.0 regardless of version used for translation ?
Got this KB Article but unable to see Knowledge Article View - Now Support Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2025 07:09 AM
Hello @Tiwarax81
I would request to test the same in your PDI and if you are able to reproduce this issue then please raise a HI Case with ServiceNow and share the solution with the community too.
Hope that helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 12:07 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 12:19 PM
- Manually Link Translations to the Correct Version:
Open the KB article record for the original article and ensure that the correct version is published.
Navigate to the Translation tab on the KB article record and check the version associated with the translation. If needed, update the version manually to reflect the correct version of the original article.
- Update the Translation After Version Change:
After updating the original article’s version, make sure that the translated version is also updated to reflect the correct version. This might need to be done manually by editing the translation record and ensuring the version field is aligned with the new version.
- Review the Translation Workflow:
If you’re using custom workflows or scripts to automate translations, check if there are any rules that force translations to always default to Version 1.0. You may need to modify the logic to ensure translations pick up the correct version of the original article.
- Check Knowledge Base Versioning Settings:
Ensure that the versioning settings in the Knowledge Base are configured to support multiple versions. Sometimes, if the versioning isn’t set correctly, it may force translations to default to the first version.
- Check for ServiceNow Updates or Bugs:
It’s possible that this behavior is related to a bug or issue in your current version of ServiceNow. Check the release notes for any known issues with versioning and translations and consider upgrading to a newer release if necessary.
