Is it not possible to use Dataflow with DB objects that have names in Korean?

[JoopKim]

I encountered the following error in Dataflow (Gen2). The source is on-premises Oracle, and both table names and column names are in Korean. Is it not possible to use Dataflow with DB objects that have names in Korean?


There are no results for query_WriteToDataDestination: Mashup Exception Expression Error Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: An error occurred while creating the Lakehouse table in the version. Basic error: The table can only contain uppercase or lowercase letters, numbers, or underscore characters. Details: Reason = Expression.Error;Message = The table can only contain uppercase or lowercase letters, numbers, or underscore characters.;Message.Format = The table can only contain uppercase or lowercase letters, numbers, or underscore characters.;Microsoft.Data.Mashup.Error.Context = User GatewayObjectId: e812cb4a-c1e2-4849-ba3e-4d5a0808c9fb

[JoopKim]

Your help has been greatly appreciated. I am glad to have identified the cause clearly. I should consider using alias instead of rename. Thank you for your diligent response.

[Anonymous]

Hi @JoopKim 
Glad that your query got resolved. Please continue using Fabric Community for any help regarding your queries.

[Anonymous · Accepted solution]

Hi @JoopKim 
Thanks for using Fabric Community.
The error message states that the Lakehouse table can only contain uppercase or lowercase letters, numbers, or underscore characters. This limitation is likely causing issues with your Korean table and column names.
Unfortunately, Dataflow Gen2 currently has limitations regarding non-ASCII characters (including Korean characters) in table names. The table names must adhere to the alphanumeric and underscore convention (uppercase or lowercase letters, numbers, or underscores). As a result, using Korean table names directly may not be possible within Dataflow Gen2.

Possible Workarounds:

While direct use of Korean table names might not be feasible, consider the following workarounds:

• Rename Tables: If possible, rename your tables to use only alphanumeric characters and underscores. For example, translate the Korean names into English or use a consistent naming convention.
• Alias Columns: If the column names are in Korean, you can still use them in your queries. However, consider aliasing them to valid English names in your Dataflow transformations.

Hope this helps. Please let me know if you have any further questions.