Unanswered

How to add Multi Language in Portal

(0) Share

Report

Posted on by Community Power Pla...

Hi Experts,

I want to enable the Spanish Language as my default language for my portal and an option to switch the language from Spanish to English.

I have flowed the below document and completed the procedure but still not able to see the option to translate my portal:

https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/enable-multiple-language-support

By default, it is opening the portal in https://www.xyz.powerappsprtals.com/en-US

I am trying to get the multi-language translation option which can translate my portal page content into different languages.

Please help me with this. any particular process which I am missing?

Thanks,

Amit

Categories:

Power Apps portals

I have the same question (0)

All responses (12)

Answers (3)

Christian Leverenz 1,214 on at

Like (0)

Report

Hi @Anonymous ,
may be a dumb reply, but did you restart the portal? Usually, those basic things are deeply cached and may not be visible immediately.
And there might be another issue: when the page you are trying to display is not available in the targetlanguage, the defaultlanguage will be shown.
Hope it points in the right direction,
Christian

Was this reply helpful? Yes No
oliver.rodrigues 9,368 Most Valuable Professional on at

Like (0)

Report
Hello, a few things to check:

did you install the language in the CDS/D365 first? https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/enable-additional-languages
In the Admin Center you also have to force the metadata translation to be re-imported https://docs.microsoft.com/en-us/powerapps/maker/portals/admin/import-metadata-translation
finally open your website record via make.powerapps.com --> Apps --> Portal Management App --> Website, there is a Default Language field that you should update
------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @OliverRodrigues and @chleverenz ,

I have followed the above-mentioned steps and I am able to get the language select option in portal:
Translation Issue

but when I am selecting the Spanish Language option then it is not changing the content language, it is still showing in English. I have also included Spanish Page Localized content in each parent pages.

Please suggest if I am missing any option.
Thanks,
Amit

Was this reply helpful? Yes No
oliver.rodrigues 9,368 Most Valuable Professional on at

Like (0)

Report

Hi
now that's weird
have you tried also other portal elements? like entity lists/entity form? is it having the same behaviour?

is the portal URL getting updated correctly? like <portal url/es-es/page?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @OliverRodrigues
Yes, it is the same for portal elements like Entity List/ Entity Form.
Also, the portal URL getting updated correctly. like <portal url/es-ES/page
You can have look in below screenshot that few contents of Entity List are changing but not the field name, Also the Text which I have created using HTML code is not changing to Spanish:
Translation Issue Entity List

Also, I am getting a weird issue for the Spanish page i.e the JS code is giving error but the same code is running fine for the English page.
for example:
if(recentJourney[0].End_Date != "")
{
}
Any Help will be appreciable.
Thanks,
Amit

Was this reply helpful? Yes No
oliver.rodrigues 9,368 Most Valuable Professional on at

Like (0)

Report

Hi, actually a few things there I can see are working fine

in regards the column/attribute names.. I am assuming that's a custom entity, that won't be translated automatically
you need first to translation in the CDS side, have you done that?
open the solution --> export translations --> open it via excel file, make your changes --> import back in CDS
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/create-solutions-support-multiple-languages#export-and-import-translations

I am not sure to why the HTML/JS are not working for your localized page, but that JS seems a bit weird for me
what type of object is the "recentJourney"?

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report
Hi @OliverRodrigues
No, I haven't done that before. Let me check on that CDS translation for Custom Entity. What about the HTML text which I created? that is not translating to Spanish automatically.
And regarding JS code "recentjourney" is a JSON object from which I am reading data.
var recentJourney = $.parseJSON( $.ajax({ url: '/XYZ/', dataType: "json", async: false }).responseText); if (recentJourney.length < 1) { //some code } else if(recentJourney[0].Journey_End!="") { //some code } else { //some code }
Thanks,
Amit

Was this reply helpful? Yes No
oliver.rodrigues 9,368 Most Valuable Professional on at

Like (0)

Report

can you share the code for the HTML?

is this ajax call from an EntityList/Odata from the Portals?
if yes, are you sure that the attribute name is correct? "Journey_End"
usually we have prefix to entity attributes like.. new_ or cr09_ etc

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi @OliverRodrigues

Below is an HTML code by which I am displaying text:
On Going Journey

And for JS code, I am calling a page where I have written a Liquid code and the output type is Json. So the name of Key in Json I have given in that way.

One more clarification I would like to have i.e If I make the CDS translation then only fields name will be translated in Entity List or its the data rows will also be translated?

Thanks,
Amit

Was this reply helpful? Yes No
Verified answer

oliver.rodrigues 9,368 Most Valuable Professional on at

Like (3)

Report

okay I think I see now where you are getting mixed up

so basically setting up multiple languages in CDS or the Portals doesn't mean it will have a translation engine behind that will translate your content.. it basically allows you to write content in multiple languages, but you have to define that content yourself

CDS/metadata translation --> if your attribute is an OptionSet then yes it will be translated via metadata
otherwise, if you have a lookup/text field, your data won't be translated here, just the attribute name
For example:
Route Name
Route 01
Route 02

in the metadata translation you will define the translation for "route name", but not the records
Nombre de ruta
Route 01
Route 02

To solve the above problem, you will need to have another attribute in your CDS entity with the spanish value
Nombre de ruta (ES)
Ruta 01
Ruta 02

now to display that in the portal you have another challenge, if that's an Entity List, you might want to have two entity list, one for English, another for Spanish, each one showing the proper fields.. now in your two localized web pages, each one can reference a specific view/entity list
another option is hiding/showing the columns via JS based on the current language
does that make sense?

now in regards the HTML content: On Going Journey
your text is hard-coded in english, so it will show always in english, it won't translate automatically.. and that's the main reason the Portals split the Web Page into a "root" and a "localized" web page, so you can have multiple localized web page, with different content in each page.. in other words, write in english in the english web page.. and write in spanish in the spanish web page
#Pro Tip
avoid hard-coding any content/text/labels in your Portal.. try as much as possible using Content Snippets
you can reference that in your HTML by the snippet name.. you don't need to worry about language, the Portals handle that itself, all you need is to make sure you have a snippet for each language (with the same name):
{{snippets['your snippet name'] }}

Was this reply helpful? Yes No