This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Paginated Reports now support all languages. The language used for report processing affects number, currency or date formatting (when using culture dependent formatters) or the processing of report expressions.
One example is the execution time expression when used with a culture dependent 'full date/time' (“f”) formatter:
Paginated_reports_supports_Power_BI_language_in_the_Power_BI_service
For “en-US”
Paginated_reports_supports_Power_BI_language_in_the_Power_BI_service
For “de-DE”
Paginated_reports_supports_Power_BI_language_in_the_Power_BI_service
Learn more on culture dependent formatters.
With this change, there is the potential to affect paginated report behavior. For instance, if your report is using an expression with a CDate function call with the date format "09-30-2024" with the Power BI language set to “de-DE” then it will now cause an error. The best practice is to use a VB date literal (ex. #9/30/2024#). VB date literals will always behave the same regardless of what Power BI language is set to.
If you hit an issue like the one above, then there is quick workaround to fall back to the same behavior as prior to this fix. Simply set the RDL Report.Language property to “en-US”.
Note: It is highly encouraged to fix the underlying issue in your RDL.
Learn more about creating paginated reports in Power BI Report Builder, creating Power BI paginated reports in the Power BI service and exporting paginated reports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.