KB33605: How to define a Translation Table with records excluding particular objects using MicroStrategy Repository Translation Wizard

The Strategy Repository Translation Tool generates a Translation Table for objects for which additional language support needs to be added. This tool supports the Search feature with which the objects to be translated can be limited. While there are four options to limit the objects to be translated as shown below, it is not possible to set the operator for Search results to be defined with 'Not In' or 'Different From' operators. 

 
This means that the condition can be defined to limit the object to be found while there is no option to exclude objects by specifying a condition. This KB provides a simple step to workaround this limitation.
 
WORKAROUND:

• Create a Translation Table using Repository Translation Tool with the second option in the screenshot: Process all objects in this project. Save the Table as T_All_Objects.
  

•  
  Notice the Translation Table is created with 6 rows.
  

• Using Repository Translation Wizard again, this time, create a Translation Table with Search like this. In this example, "Year" is used as a string to limit the objects to be translated. Then, save the Table as T_Year_Only
  

•  
  Notice the Translation Table is created with 331 rows:
  

• After two table created in the same Database, create another table based on these two table using following SQL. (Note: This SQL is for SQL Server. Please work with your DBA to adjust the syntax for your database.)
  
   
  

  
  Sql
  SELECT * INTO T_Except_Year
  FROM T_All_Objects
  
  where OBJECTID NOT IN (select OBJECTID from T_Year_Only)
  

  
  
  Check the number of rows for T_Except_Year and confirm 325 rows returned. (i.e., 331 - 6 = 325)
   
  

  
For another approach of importing only a subset of objects into the metadata, please refer to:

• KB30191: How to import only a subset of objects into the metadata using the Repository Translation Wizard 9.x