We have recently learned that PowerBI does not do a great job of URL-encoding key values.

[Udantha]

We have recently learned that PowerBI does not do a great job of URL-encoding key values.

Characters that can be used in space and externalId fields without breaking PowerBI expand functionality:

Alphanumeric characters: a-z A-Z 0-9
Unreserved characters: - _ . ~
Subset of reserved characters - no guaranties that they will always work: ! * ' ( ) ; : @ & = + $ ,

Is it possible to implement it to support all special characters as well?

[Udantha]

Hi @v-zhengdxu-msft 

Thank you for the explanation. Is there any planned development to overcome this limitations issue in the future or possibly a workaround?

[v-zhengdxu-msft]

Hi @Udantha 

Power BI does support a range of characters in URLs, including alphanumeric and certain reserved characters, by utilizing URL encoding standards. However, it's important to note that while many special characters are supported, there are specific encoding requirements and limitations to ensure compatibility and functionality.

Regarding your specific question about supporting all special characters, while Power BI strives to accommodate a wide range of characters, there are inherent limitations due to web standards and the OData protocol Power BI uses for its queries. Some characters may require specific encoding or may not be supported in certain contexts due to these constraints.

This is detailed in the Power BI documentation on URL filters, which you can review here:
Filter a report using query string parameters in the URL - Power BI | Microsoft Learn

Best Regards

Zhengdong Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.