Dynamics 365 CRM – Managing Translations in JavaScript with RESX Files

In multi-language environments within Dynamics 365 CRM, it is common to display localized messages in alerts, pop-ups, or validation logic. A robust solution is to use .resx resource files together with Xrm.Utility.getResourceString in JavaScript.

Retrieving a Translation

The standard pattern to retrieve a translated message is:

Xrm.Utility.getResourceString(
  namespace.localization.webResourceName,
  namespace.localization.messageKey
);

• webResourceName: the name of the .resx resource file, without specifying a language ID. Dynamics automatically loads the correct language based on the user’s settings.
• messageKey: the key defined in the .resx file that contains the translated message.

Best Practices for Structuring Keys

Organizing translations in a clear structure improves maintainability. Example:

const namespace = {
  localization: {
    webResourceName: "new_/localization/orderMessages",
    messageKey: "orderLimitExceededWarning"
  }
};

This avoids hardcoding strings and makes updates easier.

RESX Files for Each Language

One .resx file is required per supported language. Examples:

• orderMessages.1033.resx – English (LCID 1033)
• orderMessages.3082.resx – Spanish (LCID 3082)
• orderMessages.[LCID].resx – Other languages

For easier editing in Visual Studio Code, install the ResX Editor extension (dominicvonk.vscode-resx-editor).

Importing Resources in Dynamics 365

1. Upload the JavaScript web resource and all corresponding .resx files.
2. Assign the JavaScript to the form(s) where translations will be used.
3. If Xrm.Utility.getResourceString throws errors, check that the dependencies are set.

Setting Dependencies

Dependencies must be configured so Dynamics knows which .resx files the JavaScript relies on:

• Open the solution in classic mode.
• Edit the JavaScript web resource.
• Add the required .resx files as dependencies.

Note: Make sure to use the correct view in the solution explorer to locate your .resx files, otherwise they may not appear when setting dependencies.

Conclusion

Using .resx files for translations in Dynamics 365 CRM ensures a scalable localization strategy. Following best practices—clear structure, separate files per language, and properly configured dependencies—creates a professional and maintainable solution for multi-language scenarios.

Microsoft documentation on RESX web resources: String (RESX) web resources.