Answered

Best practice for localization PCF

(0) Share

Report

Posted on by JerryJiang

I know about using resx file to manage localization for PCF. But as the number grown in project, the PCFs have many common message like 'Confirm', 'Cancel'. If embed them into each PCF that will be hard to manage or change them.

Is there any better way to localize PCF?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Diana Birkelbach 3,072 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi @JerryJiang ,

If this seems appropriate to you, you can make a separate git repositiry only for the resx files. In the manifest you could reference the files using a relative path. I made a short test, and it seems to work.

Another option would be to make the translations in an EnvironmentVariable. Then you have all the translations in one place (but need to make a request for this).

My translation problem was more related to a lot of languages that I cannot provide out of the box. If you like the idea, maybe you could vote the it: https://powerusers.microsoft.com/t5/Power-Apps-Ideas/PCF-translations-integrated-in-the-solution-translation/idi-p/615430

Hope this helps!

Kind regards,

Diana

Was this reply helpful? Yes No
JerryJiang 5 on at

Like (0)

Report
Copy link

Link copied!

Yeah that did the trick.
Now I can put all common text into common resx file, and one more PCF specified resx file, then reference them all.
So the problem for all PCF share translation is solved, thank you!
But still it would be a problem while sharing the translation with dynamics. I have vote your idea.

Was this reply helpful? Yes No