Creating multilingual content

Creating multilingual content in Power Pages allows organizations to deliver an inclusive and accessible experience to users across different linguistic backgrounds. Whether you’re building customer portals, employee platforms, or external websites, supporting multiple languages enhances reach and engagement, especially in global or multilingual regions.

In this detailed guide, we’ll walk you through:

• Why multilingual content matters
• Supported languages in Power Pages
• Enabling multiple languages
• Translating Web Pages and content
• Using Language settings in Dataverse
• Managing language-specific components
• Best practices
• Common issues and troubleshooting
• Conclusion

---

1. Why Multilingual Content Matters

In today’s global digital ecosystem, your portal may be accessed by users speaking different languages. Offering multilingual support can:

• Improve user experience and accessibility
• Comply with regional regulations (like accessibility laws)
• Strengthen brand identity and trust
• Increase user engagement and satisfaction

Power Pages makes it possible to provide localized experiences through native language management, localized web pages, and entity translations.

---

2. Supported Languages in Power Pages

Power Pages supports multiple UI languages aligned with Microsoft’s localization standards. This includes commonly used languages such as:

• English
• Spanish
• French
• German
• Japanese
• Arabic
• Hindi
• Chinese (Simplified and Traditional)
• Portuguese
• And many others

More than 40 languages are supported, with consistent updates from Microsoft to expand and improve localizations.

---

3. Enabling Multiple Languages in Power Pages

Step-by-Step:

Step 1: Open Power Pages Admin Center

• Navigate to your site in the Power Pages design studio.
• Click on Settings > Languages.

Step 2: Enable Additional Languages

• By default, English is the primary language.
• Click + Add Language.
• Choose your desired language(s) from the list (e.g., French, Spanish).
• Save changes.

Behind the scenes, this adds language-specific settings to your Dataverse tables and Web Page structures.

---

4. Translating Web Pages and Content

Once multiple languages are enabled, every Web Page, Web Link, and Web Template can have localized versions.

Web Pages

Each Web Page in Power Pages has a Localized Content section.

Steps:

1. Go to Portal Management App.
2. Navigate to Web Pages.
3. Open a Web Page (e.g., Home).
4. Scroll to Localized Content > Click + New Localized Content.
5. Choose a language (e.g., fr-FR for French).
6. Add translated content:
   • Title
   • Copy
   • Metadata
   • Slug/Partial URL

Repeat this process for each page and each language.

Web Links & Navigation

Menus and navigation elements also support translations.

1. Navigate to Web Link Sets.
2. Open a Web Link Set (e.g., Main Navigation).
3. Add or update Localized Labels for each Web Link.

---

5. Using Language Settings in Dataverse

Dataverse also supports label translations for:

• Forms
• Entity Lists
• Columns/Fields
• Option Sets / Choice Columns

How:

1. In Power Apps, go to the Solutions area.
2. Select the table or component (e.g., Contact table).
3. Under Advanced Settings, download a Translation File (XLIFF).
4. Open and translate the contents using Excel or a localization tool.
5. Upload the file back to the solution.

Dataverse will display translated labels based on the selected UI language.

---

6. Managing Language-Specific Components

a. Custom Web Templates

If you’re using Liquid templates or custom code, use the website.language object to handle language-specific rendering.

Example:

liquidCopyEdit{% if website.language.code == 'fr' %}
  Bonjour!
{% else %}
  Hello!
{% endif %}

b. Localized JavaScript

You can also use localized scripts or messages based on the current language:

var lang = window.location.pathname.split('/')[1];
if (lang === "fr") {
    alert("Bienvenue");
} else {
    alert("Welcome");
}

---

7. Best Practices

Practice	Description
Use Language-Neutral Web Pages	Create base pages and extend using localized content.
Avoid hardcoding text	Use variables and templates for content to support translation.
Use translation tools	Automate with Microsoft Translator or XLIFF-compatible tools.
Preview each language	Use the Language Picker or modify the URL (e.g., /fr/home).
Test on various devices	Ensure all translations render well on mobile and desktop.

---

8. Common Issues & Troubleshooting

Problem	Cause	Solution
Language not appearing in dropdown	Language not enabled	Go to Settings > Languages and enable it
Translations not saving	Permissions or browser caching	Clear cache or update permissions
Content still appears in English	Missing Localized Content	Ensure you’ve created Localized versions for each element
Navigation not updating	Web Link Set missing translation	Check Web Link Labels under the right language

---

9. Testing Multilingual Pages

After enabling and configuring translations:

1. Use the Language Picker on your portal (if enabled).
2. Or, modify the URL manually:
   • English: https://yoursite.powerappsportals.com/en/home/
   • French: https://yoursite.powerappsportals.com/fr/home/
3. Test that:
   • All headings, buttons, and content are translated
   • Metadata (SEO) reflects the language
   • Navigation reflects translated labels
   • Forms and lists are displaying translated field labels