Power Query Online - '', hexadecimal value 0x14, is an invalid character.

[SergeiStPete]

Trying to connect OData endpoint, like

let
  Source = OData.Feed( "https://cloud/odata/standard.odata/$metadata")
in
  Source

and receive an error as in subject.

No problems with the same or similar queries to the same endpoint in Power BI Desktop or Excel, in browser it also works. Any ideas if workaround exists?

[Anonymous]

Hi @SergeiStPete ,

There are a few possible reasons why you are getting this error. Here are some things you can check and try to fix the issue:

Make sure that the OData endpoint is accessible and valid. You can test the endpoint in a browser or another tool like Postman to see if it returns the expected metadata and data.
Make sure that you have entered the correct credentials for the OData endpoint in Power BI Service. You can edit the credentials in the Data Source Settings under Settings > Datasets > Your Dataset Name > Data Source Credentials. You can also try to use different authentication methods, such as Basic, Anonymous, or OAuth.
Make sure that the OData endpoint supports the OData version that you are using in your query. Power BI Service supports OData versions 1.0, 2.0, 3.0, and 4.02. You can specify the OData version in your query by adding an option like [Implementation=“2.0”] to the OData.Feed function.
Make sure that there are no firewall or proxy settings that might be blocking or interfering with the connection to the OData endpoint. You can check your network settings and try to disable any firewall or proxy temporarily to see if that helps.

Troubleshooting OData sign-in errors in Power BI Desktop - Power BI | Microsoft Learn

Odata connection error from PowerBi services - Microsoft Fabric Community

How to Get Your Question Answered Quickly 

If I have misunderstood your meaning,, please provide more details.

Best Regards
Community Support Team _ Rongtie

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

[SergeiStPete]

Hi @Anonymous 

Thank you for the suggestions. The problem was in client Odata username under which account I tried to connect that dataflow. It included non-ASCII characters. After we changed it on ASCII only username everything works. Thus that is fixed.

For the information, the problem is for Power Query online only. Moreover, if copy/paste query with non-English names inside it from PBD to the service it returns an error about invalid identificator. The workaround is to copy/paste query text from one Power Query advanced editor into another, with that PQ Online recognizes such names.

I'm not 100% sure but my impression such issue appeared relatively recently, perhaps with shifting on Fabric.

[lbendlin]

Are you sure that character is not present somewhere in your Power Query code?