Forum Discussion
Helper IICulture is not supported - Paginated report
Hi,
I am currently developing a paginated report based on a PBI dataset.
The paginated report runs when there is no parameter but once I add our parameters, I run into the following issue.
I have tried changing my language in both the PBI and the paginated report but to no avail.
Has anyone else been confronted with the same issue?
How did you solve it?
Thank you
Hi JackWren , Thank you for reaching out to the Microsoft Community Forum.
This typically happens when the report's Language property is unset or dynamically resolves to an invalid value, especially after adding parameters, such as DateTime, which rely on locale for parsing.
To fix this, open your report in Report Builder, go to Report Properties and set the Language explicitly to a valid culture name like en-US or fr-FR. Don’t leave it blank or use an expression unless you're certain it resolves to a valid .NET culture string (not a numeric LCID).
This setting controls how values are interpreted during rendering and prevents the engine from defaulting to an unsupported fallback culture like 3072. Power BI's regional or workspace settings don't override this, the report-level Language setting is what matters.
If the issue persists, check if any parameter expressions indirectly influence locale or formatting. You can also temporarily output =User!Language in a textbox to see what the engine is resolving at runtime.
Expressions in Power BI Report Builder
[MS-LCID]: Windows Language Code Identifier (LCID) Reference
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
1 Reply
v-hashadapuCommunity Support
Hi JackWren , Thank you for reaching out to the Microsoft Community Forum.
This typically happens when the report's Language property is unset or dynamically resolves to an invalid value, especially after adding parameters, such as DateTime, which rely on locale for parsing.
To fix this, open your report in Report Builder, go to Report Properties and set the Language explicitly to a valid culture name like en-US or fr-FR. Don’t leave it blank or use an expression unless you're certain it resolves to a valid .NET culture string (not a numeric LCID).
This setting controls how values are interpreted during rendering and prevents the engine from defaulting to an unsupported fallback culture like 3072. Power BI's regional or workspace settings don't override this, the report-level Language setting is what matters.
If the issue persists, check if any parameter expressions indirectly influence locale or formatting. You can also temporarily output =User!Language in a textbox to see what the engine is resolving at runtime.
Expressions in Power BI Report Builder
[MS-LCID]: Windows Language Code Identifier (LCID) Reference
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.