When using Import set to register translated text record, Documents field is empty.

[ubido]

Dear folks,

I'm having the same problem as described in this post from about a year ago:

https://community.servicenow.com/community?id=community_question&sys_id=936d4be9db9cdbc01dcaf3231f96...

And I applied the same solution and it did not work; what I'm doing is trying to use an import set to translate a few catalog items contained in an order guide to French. I did the translation manually in our development instance and exported the entries from the sys_translated and sys_translated_text to a couple of Excel files.

I successfully imported sys_translated into our QA instance, but when I try to do the same for sys_translated_text, the Document field only has an "(empty)" value. However, when I open the record the information is there and I'm actually able to save the record again by manually reentering the expected value for the Document field. But this is not practical and defeats the purpose of using an import set (given that I have tons of translations to do).

I'm including the following fields in the Excel file I'm trying to import:


Document
Field Name
Table Name
Document Sys ID
Value
language


This is following the recommendation in the link above, but then now the document information is not there (originally I was not including the Document Sys ID field). My apologies if this has been answered before, but I have been looking in the community site for a solution unsuccessfully. If somebody has answered this question before, please provide the URL to the correct answer or help me find the solution for this one.

The enclosed screen shots show the resulting entries in the Translated Text.

Best regards,

ubido

[jaloftas]

In the import set you are using do you have the sys_id of the target record populated in the document_sys_id field? Could you past an image of what a few rows of your Excel import looks like which includes all the columns?

[ubido]

jaloftas,

Sorry for the delay in responding; for some reason I did not see your message even though it says here you posted it two days ago...weird.  Anyway... I actually solved this issue yesterday and I was in fact using the sys_id field instead of the documentkey  field.  Once I was able to export my translation field in a format that included this last field everything worked.  

In the enclosed image you will find the Excel import file I used and which I created by using the Show XML option in the translated_text file.  This has the advantage of using the actual field name, so when I create the map the auto matching option makes things even easier on the import side.

Let me know if this is what you requested.

Regards,

ubido

[denis hoffmann]

Hi,

since "Document" (aka 'documentkey') is a "Document ID" type field,

in your transform map do you map the display value or the sys_id of your Document ?

[ubido]

Denis,

I've tried that as well, and the result was that the "Field Name" field is now empty as well (see the resulting entries in the first screen capture I'm enclosing).  The second screen capture shows part of the source file I'm trying to import; I matched the Document Sys Id (column D) against Document in the target file as you seems to suggest but it didn't work.

I suspect that you're onto something as all the document I've found in Service Now's KB points to the sys ID field as the culprit.

Thanks for your reply.

Regards,

ubido