Model-driven app translations not showing for French (Canada) / Quebec

(0) Share

Report

Posted on by Charles Seguin

401

Hello!

Our organization is based in Quebec, so making apps available in French is a must. I designed a model-driven app for a business-critical application. The base language for our environment is English (United States), ID 1033. French (France), ID 1036, is also enabled in our environment. Through the Solution, I exported all the English strings and translated them to French. Imported the translations successfully back into Powerapps.

Problem is, the translated strings aren't showing up when the user uses the app. Oddly, all the "system" strings are shown in French (such as Home / Acceuil), but none of the "custom strings" that I translated are showing up. Re-exported all the translations and, sure enough, they are loaded.

I think the problem may be that my users aren't using French (France), ID 1036, but rather French (Canada), ID 3084 as their system language. However, I can't enable French (Canada), ID 3084, in the Admin Center. Only 1036 is available (see screenshot below).

Providing employees in Quebec with French-language tools is not only a nice-to-have, it is a legal obligation. Plus, I spent quite a bit of time translating 2300+ strings... couldn't wait to get back to coding after that was done! 😉

Any idea how I can get my translations to show in my model-driven app?

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

Sort by

v-bofeng-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CharlesS :

I think this should have nothing to do with system language. As long as you configure the translation file (ID 1036) correctly, it can take effect (I've made a test and it worked well).

In addition, to enable this feature, users need to make personal settings:

1\Open this Moden Driven app

2\Select Personalalization Settings

3\Set User Interface Language

Best Regards,

Bof

Was this reply helpful? Yes No
Charles Seguin 401 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for your reply @v-bofeng-msft !

We checked the user's personal options: the settings seem to be correct.

Perhaps my translation file is not setup correctly? I was able to successfully import the translation XML file, which has three tabs:
1. Information : No changes made here. Base language is English (United States) 1033.
2. Display string: This tab is completely empty.
3. Localized Labels: All my original 1033 strings are in the first column and all my French translations are in the 1036 column, as such:

Am I missing something?

Thanks!

Was this reply helpful? Yes No
v-bofeng-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CharlesS :

Your operation does not seem to have any problems, I also tested it like this. But I did not have the problem you mentioned.

Maybe you could check the translation file again and try to import it again.

If this problem cannot be solved,I suggest you create a support ticket.

Best Regards,

Bof

Was this reply helpful? Yes No
Verified answer

Charles Seguin 401 on at

Like
a
(0)

Report
Copy link

Link copied!
Good news! I was finally able to fix this problem. Turns out it is not a language issue, but a security role issue.

Here is the problem and how I resolved it:
I had set up my security roles from blank, denying all permissions by default and only granting what I thought were the minimum necessary permissions to execute the task at hand.
I could not find any precise definition of the meaning of each permission. It turns out that one of the cryptic permissions was associated to the ability to view help panes in local languages. I did not have the time to test every single permission to find out which one was responsible for this issue.
So I created a new security role, based on the Basic User role. I removed a few privileges (which are unacceptable for my organization, such as the ability to export to Excel) and added the required privileges for my custom entities...
And Voilà! Help panes now show in the user's language!

Moral of the story: don't create security roles from scratch. Use the most restrictive standard security role as your baseline template and build from there.

Was this reply helpful? Yes No
v-bofeng-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CharlesS :

Glad to learn that you solved this problem, and thank you very much for sharing the solution.

Best Regards,

Bof

Was this reply helpful? Yes No