Empty cells under default language in translation table are overwritten when .mmp packages is from older versions are migrated to MicroStrategy 2021 Update 9

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
In the releases prior to 2021 update 9 when migrating Object Manager packages containing Dossiers/Reports/Documents on which empty cells under default language in translation table were present (let’s put aside the discussion if leaving blank translations for the default language is considered best practice or not), the Translation table would remain unchanged after the import to the target environment. However, the behavior has changed together with version 2021 Update 9 (as a part of fix for another defect).
 
Starting with 2021 Update 9 in the described scenario empty cells of the default language will be overwritten by one of the remaining translations. Very often it’s Chinese (Traditional) if a translation in this language is available (When migrating an object by a package, Strategy will use the object’s translation string of the smallest locale code (Chinese Traditional, ID 1028) to fill the default locale’s translation(English, US, 1033) if it is empty.) 
 
The current behavior is similar to the one described in one of the old KB articles reaching back to the Strategy 9.4.1 - KB46488: https://community.strategy.com/article/KB46488-Object-translations-are-changed-for-the-default-language?language=en_US 
 
 

Example: 

 
Source Environment: 

 
Target Environment: 

Conclusion:  

Our logic to handle the object's translations during the import can be summarized as: 

• If the target project has an object's all translation locales, its empty translation in default locale won't be overwritten. 
  
• if the target project doesn't have an object's all translation locales, its empty translation in default locale will be overwritten by the translation of the object's smallest locale which the target project doesn't have. 
  

Solution: 

 
If we want to leave the default locale’s translation empty after the import, here is a workaround:
 
Add all locales where the object has related translations to the target project. In this issue, we should add following locales to the target project. One thing to mention, we should restart the I-Server to make this change work.