If you’re using custom properties (or custom fields) and you change your language preferences in the user interface, you may notice these fields vanish from saved custom reports and the column chooser for grid views.

For example, if the original custom properties are coded for French, and you switch between English and French within your browser language preferences, then run reports while the user preference is set to English.

The following error is shown: The given key was not present in the dictionary.

Usually, changing languages is not an issue. However, custom properties require SQL coding to be created and run for each translation in the database when you need to change languages in the user interface. Use the steps below to create translations for your custom properties.

Solution

FlexNet Manager Suite

1. Locate the database table UIItem and find the custom properties.
2. Use the information from this table to check database tables ComplianceResourceString and ResourceStringCultureType.
3. Run a SQL command like the example below to create the missing translation in the database for your chosen browser language.  

Using the example for this article, translating from English to French:

EXEC CustomPropertyUpdateDisplayName @Name = custompropertyname, @CultureType = 'en-US', @DisplayNameInPage = ‘translation name', @DisplayNameInReport= 'translation name’

This will add strings for the custom properties that are missing for end users in their language.

Options include: German ('de-DE'), Spanish ('es-ES'), Japanese ('ja-JP'), English ('en-US'), and French ('fr-FR')

Flexera One IT Asset Management

As a workaround, you can set the browser and the user’s language preferences in Flexera One IT Asset Management back to the original language that was selected for the custom properties.

If you need the custom properties to support more languages, create a support case detailing the issue and list what language the browser and user preferences are currently configured to use.