Step 7 (Optional): Localize the BDC Model File (Metadata.bdcm)
Published: July 2010
This step shows how to localize custom items in the BDC model file and contains a list of locale ID values that are supported in the BDC model file.
Usually, the values in the BDC model file (metadata.bdcm) do not appear in the user interface. But in some cases, you might have to localize this file to show some customized items in localized languages, such as the customized Outlook form column name.
Localizing the BDC model file is different from localizing other XML files in the declarative Outlook solution. The BDC model schema enables you to add localized strings as additional XML nodes, as shown in the following example.
<LocalizedDisplayNames> <LocalizedDisplayName LCID="LCID value">Localized string</LocalizedDisplayName> </LocalizedDisplayNames>
You can include all supported languages in the same BDC model file, so that the display names for those BDC entities will change according to the Office language settings. The following example shows how to include three languages in the BDC model file.
<LocalizedDisplayNames> <LocalizedDisplayName LCID="LCID value1">Localized string1</LocalizedDisplayName> <LocalizedDisplayName LCID="LCID value2">Localized string2</LocalizedDisplayName> <LocalizedDisplayName LCID="LCID value3">Localized string3</LocalizedDisplayName> </LocalizedDisplayNames>
For a list of locale ID values to use for the LCID attribute, see Table 1 later in this topic. For more information about LCIDs, see What is the LCID.
The BDC model schema enables you to add the LocalizedDisplayNames nodes as child nodes under different BDC entities, as shown in Figure 1. The nodes labeled Loc Node in the diagram represent the LocalizedDisplayNames nodes. For more information about the BDC model schema, see BDCMetadata Schema. For more information about the BDC model file, see Step 1: Create the BDC Model (Metadata.bdcm).
Table 1 lists the locale ID values that you can use in the BDC model file.
Ukrainian - Ukraine