Power BI Paginated Report Multi-Lingual Prompt Issue - Please Assist

[Corinna_StAubin]

Hello, 

Need assistance with Power BI Paginated Reports Multi-lingual Prompts

Background: 

Working with a client in Power BI Report Server & Paginated Reports.  We have built several (over 100) Power BI Paginated Reports embedded into clients web app.  

Client selects in the web application their language: English, French, Japanese, Chinese, German

The language selection is stored in a SQL database.  All the reports (body of reports) properly display the language selection. 

Issue:  Parameters are always displaying English language and not the language selected. 

Expression:

=iif(IsNothing(Lookup("employee_id", Fields!TranslationKey.Value, Fields!TranslatedText.Value, "UserDetails")),"Employee ID",Lookup("employee_id", Fields!TranslationKey.Value, Fields!TranslatedText.Value, "UserDetails"))

What needs to be done for the Parameters to also display the language selected?  The report body as previously stated works perfect and displays the language selected throughout, it's just the parameters that are not displaying the proper language selection. 

Please Help

[v-achippa]

Hi @Corinna_StAubin,

Thank you for reaching out to Microsoft Fabric Community.

The report body can use Lookup() or dataset Fields, so your placeholder expression with Lookup works. Parameter prompt expressions cannot use dataset fields or Lookup(). That is why your Lookup approach that works in the body fails for the parameter area and the prompts stay in English.

Since the reports are embedded in a custom web application and the app already controls the language selection, the recommended approach is to hide the SSRS parameter pane and render localized parameter prompts directly in your application UI.

Then pass parameter values(including language) into the report and when calling the report pass values using rp:ParameterName=value in the URL or by the embed API.

This avoids SSRS limitations, keeps translations consistent and works across all your reports.

Thanks and regards,

Anjan Kumar Chippa

[Corinna_StAubin]

This works for SSRS but not for Power BI Paginated Reports as options are not available in Paginated reports as are in Power BI Paginated Reports.  Please correct if we are wrong and provide more details.  When we apply the syntax an error is thrown.

[v-achippa]

Hi @Corinna_StAubin,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Corinna_StAubin,

We wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[Corinna_StAubin]

Need additional assistance as not working in Power BI Paginated Reports.

[v-achippa · Accepted solution]

Hi @Corinna_StAubin,

In Power BI Paginated Reports the parameter prompt field does not support expressions like ssrs, this is a current limitation. For multi lingual scenarios, the supported approach is to localize the parameter Available Values through a dataset query, so that the dropdown contents reflect the user’s language.
Or since you are embedding the reports in a custom web app, hide the built in parameter panel and provide your own localized parameter UI in the app, then pass the parameter values directly into the report at render time.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Corinna_StAubin,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[Shahid12523]

Problem: Parameter prompts in Power BI Paginated Reports don’t auto-translate like the report body.
Fix: Use an expression in the parameter’s Prompt field:
=Lookup("employee_id", Fields!TranslationKey.Value, Fields!TranslatedText.Value, "UserDetails")

Or use User!Language logic to switch labels based on language.
⚠️ Heads-up: A known bug may cause prompts to revert to default names after selection. Microsoft is working on it.

[Jaspreet99]

@Shahid12523

Just a note here. I see you’re posting replies almost every minute. That kind of pace makes it seem like these are auto-generated rather than genuine contributions. If it’s only generic answers, people might as well go straight to GPT instead of coming here. The real value is when we share fixes we’ve tried or insights from our own work.

I’ll mark this one as inappropriate since it doesn’t feel in the spirit of the community.