Salesforce

WorldServer - how to search a Translation Memory based on the Entry Origin and using wildcard ("*")

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWorldServer
Symptoms/Context
When searching for all Translation Memory entries coming from a specific project, I am using the Search based on Entry Origin. I am using the Source folder path as displayed in the Task History of the project and I expect to find the results related to all files in the project. However, I get no results. For example, this is a search based on Entry Origin entered as:

/root/Projects/2975_Test Belarusian/Source-English (United States)

User-added image
Resolution
If you want to do a search based on Entry Origin for a project that contains multiple tasks/files and you want to display all entries associated with all files belonging to the project, you need to use a wild card after the project's source folder path. In the example above, use

/root/Projects/2975_Test Belarusian/Source-English (United States)*

and you will see the results:

User-added image

You could also just use the project group ID to search all entries associated with a project group. The project group ID is the number in the directory that precedes the project name. Following the current example, the complete entry origin includes the project group ID 2975. You could enter the search *2975* to find all entries associated with this project group ID:

User-added image

The same applies to searching for the project name, which is also always part of the Entry Origin. Following the same example, you could search for *Test Belarusian* and find all TMs associated with this project (for all languages):

User-added image

Following the same principle, you could search for all TM entries associated with a specific file name, for instance, *This is a house.docx*



 
Root Cause
Possibly, the specific file included in the Entry Origin path did not contain any new translation. Therefore, no result was found. If you use the * wildcards in Entry Origin path search, you will get all results associated with the project.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by