Localization export/import between development and production system

PIERRE-LOUIS_DURRIS

I am adapting lot of things in the localization and I would like to know if this is possible to export from one of our system and import to another one. I have looked at KB 1123 and maybe using API is an option but don't know if possible on our environment.

Nicholas_Velich

We do not have any pre-existing tools available to do so, but it is possible to export/import via SQL. The localization keys are all stored in the DisplayString table in the ServiceManagement database.

The individual commands are something like this...

To Select All Localization Keys

SELECT LocalizationKey,DisplayStringOverride

FROM [DisplayString]

WHERE (LocaleID='Locale') AND LocalizationKey IS NOT NULL

ORDER BY LocalizationKey

To Insert a New Key

INSERT INTO DisplayString (ElementID, LocaleID, DisplayString, LocalizationKey)

VALUES ('GUID', 'Locale', 'Translation', 'LocalizationKey');

To Update an Existing Key

UPDATE DisplayString

SET DisplayStringOverride='Override'

WHERE (LocaleID='Locale') AND LocalizationKey='LocalizationKey'


Direct ServiceManagement database table modification like this is not supported via typical channels, but does work just fine if done correctly. Remember that all GUIDs need to be unique, and all Locale/LocalizationKey pairs must be unique.

...and remember, before playing with these tables at all, please perform a database backup.  

Thanks,
Nick

PIERRE-LOUIS_DURRIS

Thank you for your feedback. I'll test it

Nicholas_Velich

We do not have any pre-existing tools available to do so, but it is possible to export/import via SQL. The localization keys are all stored in the DisplayString table in the ServiceManagement database.

The individual commands are something like this...

To Select All Localization Keys

SELECT LocalizationKey,DisplayStringOverride

FROM [DisplayString]

WHERE (LocaleID='Locale') AND LocalizationKey IS NOT NULL

ORDER BY LocalizationKey

To Insert a New Key

INSERT INTO DisplayString (ElementID, LocaleID, DisplayString, LocalizationKey)

VALUES ('GUID', 'Locale', 'Translation', 'LocalizationKey');

To Update an Existing Key

UPDATE DisplayString

SET DisplayStringOverride='Override'

WHERE (LocaleID='Locale') AND LocalizationKey='LocalizationKey'


Direct ServiceManagement database table modification like this is not supported via typical channels, but does work just fine if done correctly. Remember that all GUIDs need to be unique, and all Locale/LocalizationKey pairs must be unique.

...and remember, before playing with these tables at all, please perform a database backup.  

Thanks,
Nick

PIERRE-LOUIS_DURRIS

Thank you for your feedback. I'll test it