Exam PL-200 topic 1 question 49 discussion

1- Export/Import 2-Separate Component 3-Separate Component For 2 and 3, see supporting information here - https://learn.microsoft.com/en-us/power-platform/alm/create-solutions-support-multiple-languages

View -- Export & Import translations Email Template -Separate Component for each language Report - Separate Component for each language

1.Export and import translations 2. Separate component for each language 3. Separate component for each language

1.Export and import translations 2. Separate component for each language 3. Separate component for each language Reference Link: https://learn.microsoft.com/en-us/power-platform/alm/create-solutions-support-multiple-languages

1. export then reimport 2 & 3. separate component for each language https://learn.microsoft.com/en-us/power-platform/alm/create-solutions-support-multiple-languages

if you don't have the translations you cannot use them of course. So maybe for 3) it is 'First, export import. Second, use Localized labels aka embedded labels (aka...) depending on the user settings. I guess PowerBI can do this. SSRS... hmm I would never ever use this? So still not clear if 3) is embedded now that I have seen this 1 documentation (before i would have rejected it because the correct term is 'Localized Labels')

The difficult thing about these questions is the inconsistency of how microsoft uses expressions. I have the impression, microsoft has added more ambiguity adding new or not so hard cut definitions. Basically, in the translation sheet the reference is <Worksheet ss:Name="Localized Labels" ss:Id="Localized Labels" ss:Protected="1"> also here: localized label. https://learn.microsoft.com/en-us/power-apps/maker/data-platform/export-customized-entity-field-text-translation in constrast to that, here, we have 'embedded labels' but it does not say if it can be used in reports. ... Sometimes plural, singular is important, sometimes not. https://learn.microsoft.com/en-us/power-platform/alm/create-solutions-support-multiple-languages: Embedded labels Each of the solution components that use this tactic requires that any localized text be included in the solution component. // is it literally 'embedded'? Embedded into what?

If this is about SSRS reports than you could query the users language and then have a dynamic expression inside the "embedded labels" to set different content based on language. You could also create a custom "Report Labels" table and query from there based on the language. Then use the "Lookup" function to get the one appropriate for the report component and users language. Creating a copy of a report and just translating the labels, but becomes messy when you need to do changes to it (and need to repeat it "no of languages" times). So I'm not sure which answer it is.

Does this kind of question allow to use the same option twice??

view: export and re-import translated text email template: create a separate version for each language report: create a separate version for each language