Error: Translation Management for Knowledge Articles

Joe85
Tera Expert

We've recently activated Translation Management for our Knowledge articles and are experiencing an issue with existing translated versions. When we try to update the translation of an article that was already translated, ServiceNow is creating version 0.1 vs 1.1 or 2.1, etc. This is resulting in a new article with a new KB number but for the same topic and language as an existing article.

For example, we have an article published in English with a French version. We update the English and publish v2.0. Then we click Translate and update the French, but instead of making French v2.0, the system makes a second French article and now we have two French articles that are both version 1.0. It's like the English and French versions are not linked, but I checked and the English version is the parent to the French article.  

What's odd is if I create a new article with French translations everything works as it should and the system will create a French 2.0 version if I update the translation. The problem only seems to happen with articles that were translated via the old method (prior to activating Translation Management). 

1 ACCEPTED SOLUTION

@Alex Coope Thank you for your response. We found the issue to be that out of the box the system was looking for a parent article version 1.0 and if the parent article was 2.0, 3.0, etc. the system would create a new translated version instead of updating the existing one. To fix this our developers changed the script to look at the parent article no matter what version it is. This seems to be working for us.

Thank you for your help.

View solution in original post

2 REPLIES 2

Alex Coope - SN
ServiceNow Employee
ServiceNow Employee

@Joe 

Apologies for the late reply, I believe this is due to some Restricted Cross Scope privileges that need to be approved. Once approved it should be as expected,

Many thanks,
Kind regards

--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization

@Alex Coope Thank you for your response. We found the issue to be that out of the box the system was looking for a parent article version 1.0 and if the parent article was 2.0, 3.0, etc. the system would create a new translated version instead of updating the existing one. To fix this our developers changed the script to look at the parent article no matter what version it is. This seems to be working for us.

Thank you for your help.