Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now

0

Date range slicer input not working when service language is set to Bulgarian

Hello,

 

After April 1st, the following issue emerged in the Power BI Service. If the consumer's service account language is set to Bulgarian (Български), the consumer is unable to change dates in a date range slicer. This applies both to manual input and calendar pop-up input. All consumers have PRO licenses.

 

Here are the steps to reproduce:

  1. Set your service language to English
  2. Open a report with date slicer
  3. Make changes to the date range via calendar popup or manual input [SUCCESS]
  4. Set your service language to Bulgarian (Български)
  5. Open a report with date slicer
  6. Make changes to the date range via calendar popup or manual input [FAIL]

 

This behavior applies to all date range slicers. 

 

A workaround is to change the slicer type to Relative date picker or add a slider.

 

Here's how the slicer looks with service language set to English:

Service language set to EnglishService language set to English

 

Here's how the slicer looks with service language set to Bulgarian:

Service language set to BulgarianService language set to Bulgarian

Status: Delivered

Hi @314chart ,

 

I have got reply from the product group said they had filed the bug and it should be fixed in 4-5 weeks. Please be patient for the fix. Thanks for your understanding!

 

Best Regards,

Caiyun Zheng

Comments
v-cazheng-msft
Community Support
Status changed to: Accepted

Hi @314chart ,

 

I can repro it and have reported it internally(ICM 301445608). Will sync here once there is any update from the product group. Thanks for your understanding!

 

Best Regards,

Community Support Team _ Caiyun

v-cazheng-msft
Community Support
Status changed to: Delivered

Hi @314chart ,

 

I have got reply from the product group said they had filed the bug and it should be fixed in 4-5 weeks. Please be patient for the fix. Thanks for your understanding!

 

Best Regards,

Caiyun Zheng