Import Strings

Strings requiring updates are exported first, then updated in the exported sheet, and re-imported. This functionality can be used by a Workspace Administrator to apply changes across the entire workspace, or by a Community Administrator to tailor strings to meet the specific needs of an individual community.

Role Permissions

1. Workspace Administrator: Imports customized or translated strings that apply across the entire workspace, accessed via Settings >> Workspace >> Customization >> Language and Strings >> Import Strings.
2. Community Administrator: Imports customized or translated strings scoped to an individual community, accessed via Settings >> Community >> Community Configuration >> Strings >> Import Strings.

Steps to Import Strings

Importing strings is completed in four stages: exporting the strings, updating the exported sheet, uploading the completed sheet, and receiving confirmation of the result.

Export Strings

Strings are exported first. Help Article for Export Strings

Once exported, the Excel sheet displays the following columns:

1. Strings: Displays the string identifier, e.g., application.ideascale.ml.6.digit.code.
2. English Text: Displays the original, uncustomized text, e.g., 6 digit code.
3. English Unverified: Displays only text that has already been customized, e.g., 6 digit code customized.
4. Customized/Verified: Left empty by default, so a new customized value can be entered for import.

Update or Customize the Strings

The last column, Customized/Verified, is updated with the desired changes in the exported sheet.

The sheet shown above was exported for the English language, so the third column appears as English Unverified. For another language, such as Spanish, the third column is labeled accordingly:

Any number of strings can be customized, from a single string to the entire sheet, with no restriction on how many are updated.

Import the Strings

Once the sheet is ready, the Language for the import is selected, the completed file is uploaded, and Save is selected.

A confirmation message reading "Languages and Strings were imported successfully" appears at the top of the screen once the import completes.

Import Confirmation Email

On completion of the import, the Workspace Administrator or Community Administrator who performed the import receives an email notification confirming the result.

See Exceptions below for strings that are not imported. When the notification lists strings that were not uploaded, it includes the row number of each affected string in the exported Excel sheet. The listed row can be located in the sheet, and the string copied from it, then searched for in the Language and Strings section, updated, and saved directly.

If an error occurs during the import, an email notification specifying the error is sent instead:

Once updated, the Customized checkbox appears checked next to the string, along with the new customized value. The example below reflects strings updated in the Spanish language:

Exceptions

1. HTML Content: Strings containing HTML are not imported, since HTML support was recently discontinued.
2. Strings Not Imported: When a string is not imported, the import confirmation email lists the row number of that string in the exported Excel sheet, so it can be located, copied, and updated manually through the Language and Strings section.

Frequently Asked Questions

What is the purpose of the Customized/Verified column in the exported sheet?

The Customised/Verified column needs to be populated with a new, customised value for each string that needs to be updated before the sheet is re-imported.

Is it necessary to customize every string in the exported sheet?

No. Any number of strings can be customized, from a single string up to the entire sheet, with no restriction on how many are updated.

How is confirmation received that a string import was successful?

A confirmation message reading "Languages and Strings were imported successfully" appears at the top of the screen once the import completes, and the Workspace Administrator or Community Administrator who performed the import also receives a confirmation email.

Why would a string fail to import?

A string fails to import if it contains HTML. The import confirmation email lists the row number of any string that was not imported so it can be located and updated manually.

Does importing strings work differently at the workspace level compared to the community level?

The import steps are the same at both levels. A Workspace Administrator accesses Import Strings through Settings >> Workspace >> Customization >> Language and Strings to apply changes across the entire workspace, while a Community Administrator accesses it through Settings >> Community >> Community Configuration >> Strings to apply changes within a single community.

Related Articles

• Help Article for Export Strings
• Help Article for Language Settings
• Help Article for Community Configuration