Loading

Translation Workbench Export and Import Troubleshooting and Support

게시 일자: May 28, 2026
상세 설명

It is not within the scope of Salesforce Support to analyze and review the resulting export and import files to identify, correct or resolve Common Errors with Exporting and Importing Translation Files resulting from client side file manipulation.

The resulting translation import log file will contain pertinent error details. Customer's will need to review and address errors client side in order to update and correct the translation files for resolution.

File manipulation to correct outlined error conditions is not within the scope of Support or Admin Assist's offerings. Editing and modifying translation files on customer's behalf or performing exports and imports in customer environments is prohibited.


Note: However, if an import or export fails after multiple attempts with the following unexpected errors, please log a case with Support for further investigation.

Your export request failed. Please retry or contact support.

Your import request failed. Please retry or contact support.
 
솔루션

Best practices and recommendations for Translation Workbench

 

  • Only export and import translation files from the same organization. It is not recommended or supported to export a translation file from one Salesforce environment such as a sandbox and import it into a different sandbox or production environment.
 
Differences in customizations or metadata between the export file's source environment and the target environment or between the time the export file was generated and the import was performed may result in "Invalid Key" errors. This is expected behavior and by design, correct or remove the components references resulting in the error from your translation file.

 
  • Remove any components from the translation file that are not being directly translated for import. Keeping untranslated components in the file increases the potential for errors or other unexpected conditions.

If untranslated components are kept in the translation file, it is expected for resulting logs to contain the following message for each untranslated component:

Missing translation for: <ComponentType.ComponentAPIName>
 

Troubleshooting Recommendations:

 

  • The resulting translation import log file will contain pertinent error details. Customer's will need to review and address these errors client side in order to update and correct the translation file.

 

  • If your translation file is large, attempt splitting the file into multiple smaller translation files. This may allow you to more easily identify whether the errors are related to specific subsets of translation data.

 

  • Troubleshoot and resolve errors received by re-attempting translation file operations. Import, review log data and errors, correct the translation file and then re-import. This process may take several attempts to identify and resolve all errors conditions for a successful operation.
Knowledge 기사 번호

000393190

 
로드 중
Salesforce Help | Article