Arabic text not showing up

[Anonymous]

Hello Friends

I am requesting your help to resolve an issue.

I am using table visualization on Power BI Desktop October 2017 (Optimized for Report Server).

Data connection is using direct query.

There are some names in Arabic in the data source.

These do not show up in the table visualization. However, when I open Edit Queries, the arabic text shows up fine.

Please help me to resolve this issue.

Many Thanks

Sukhomoy

[Evander_Latine]

Have the same issue

[MARSLAN80]

SAME PROBLEM HERE!

in excel i can read the arabic charaters good.

 in the powerbi table the data still good,

but when place slicer the names shown as cheicken feets.

any idea how to solve this

thanks

[MARSLAN80]

[v-chuncz-msft]

@Anonymous,

I can not reproduce this issue. Share us an example if possible.

[Anonymous]

@v-chuncz-msft

Its a bit difficult to show the example as we are using data for our client and we are using enterprice version of power BI with data policy. 

Backend Database is Teradata. 

Although I am tring my best to describe the issue. 

We have a list of Customer Name, mixed with Arabic and English Text. Which needs to visualize in a Table or Matrix. 

According to our investigation, we have tryed to find the data from Query Editor, By 

Edit Queries > Queries > Select - Table Name : 

we find the data is showing Arabic and English both.  

But in Power BI area, when we are using Table or Matrix Visualization to List the customer name, it is only showing english name, no arabic text is visible. there is no error messege as well.

We are using ODBC with UTF8 character set for SQL Assistent as Query Development Tool.

We have tryed to visualize data through Oracle Data Visualizer through the same ODBC, and it is working fine.

But we are unable to use ODBC Data source in Direct Query Mode in Power BI. 

Hence, we are stuck. now there is only option to move the project from Power Bi to ODV, if there is no solution. 

[hmortada]

I'm facing the same issue here ... did you find any solution or workaround?