Localizing Display Names of Custom Properties

FlexNet Manager Suite 2023 R1 (On-Premises)

Execute the following in SQL Server Management Studio against your FNMSCompliance database, once the custom properties already exist in the database.

EXEC dbo.CustomPropertyUpdateDisplayName
        @Name = 'My-Unique-Name',
        @CultureType = 'ISOCultureCode',
        @DisplayNameInPage = 'Prompt value',
        @DisplayNameInReport = 'Column header'
        

where

Type	Value
@Name	Mandatory. The internal name (in code and database) of your custom property, declared when you added it to the database. Never localize this internal name.
@CultureType	Mandatory. A five-character ISO culture name (enclosed in single quotation marks). The permitted values are available at http://msdn.microsoft.com/en-us/goglobal/bb896001.aspx. This is the culture for the localized values in this declaration. Notice that localized values are only displayed in FlexNet Manager Suite when your enterprise has installed the corresponding language pack that provides localized values for the factory-supplied controls as well.
@DisplayNameInPage	Mandatory. This is the localized label (enclosed in single quotation marks) displayed on the tab in the web interface for FlexNet Manager Suite when the culture setting for the interface matched the one you declare in CultureType.
@DisplayNameInReport	Mandatory. The localized label (enclosed in single quotation marks) that is available for you to include in custom reports that display this custom property.

You can repeat this procedure as often as required to define localized display names in all cultures in use in your enterprise.

Tip: The appearance of the web interface for different locales is controlled in two separate places:

• The formatting of dates and numeric values is taken from the settings on your web browser.
• The language presented in the web interface is controlled in the My Preferences page under the your account name > My Preferences menu in the top-right corner of the web interface. Options for other languages are only present when your enterprise has purchased appropriate language pack options.

This separation allows for the common case where a single language (such as English) may have different date formats (such as 12/31/19 and 31/12/19) in different parts of the world.