Salesforce

WorldServer: Error "can not parse content from null" when opening a MultiTerm Server termbase

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer 11.x
Trados GroupShare 2020 SR1 CU4
Symptoms/Context
When opening a MultiTerm Server termbase you have connected to your WorldServer instance, you see an error similar to the one below:

Could not find attribute in map
Resolution
 

Defect

A defect has been logged with our Development Team, and a fix is expected in a future release of WorldServer.
 

Workaround

  1. Use MultiTerm Desktop to save the termbase definition file (.xdt file), and then to export the data (.xml file).
     
  2. Use a text editor such as Notepad++ to open the termbase definition file (.xdt).
     
  3. Search within the file for the name of the field/attribute mentioned in the error message, and note down the capitalisation (e.g. Term Description).
     
  4. Close the definition file, and open the termbase export file (.xml) in the text editor.
     
  5. Perform a search/replace using the Match case option and replace all occurrences of the field/attribute as they appear in the error message (e.g. Term description) with the correct capitalisation you found in step 3 (e.g. Term Description). Save the file when done.

    Replace All
     
  6. Recreate the server-based termbase using the export file (.xml) that you modified.
     
  7. Connect the recreated termbase to WorldServer.

NOTE: You may have to repeat steps 2 to 7 if more than one field name is not correctly capitalised in the termbase entries.

 

Root Cause
WorldServer maps an attribute (not visible in the WorldServer attributes list) to each field defined in the termbase definition, and then reads the fields from the termbase in a case-sensitive way. If one or more of the terms in the termbase have one or more fields where the case does not match that of the definition, WorldServer will throw an error as it does not believe the corresponding attribute exists.

For example if the definition is as follows:

Termbase Definition

Entries with field names as below will be fine:

Correctly Capitalised

But entries with field names such as the one below will prevent WorldServer from opening the termbase:

Incorrectly Capitalised
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by