- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Name-based column mappings
I was hoping to leverage .option("delta.columnMapping.mode", "name") to remove underscores from my column names and make more user friendly fields. However, when I write the table to the Lakehouse, it doesn't appear in the SQL Analytics endpoint, and doesn't appear in the semantic model.
It looks like the issue is related to this.
Delta Lake table format interoperability
Is there any hope that Microsoft will expand the Delta Lake table format interoperability (considering that is what a lot of this is built on?)
It would be nice if Fabric worked as a universally compatible suite of tools.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @jjaeger94 ,
It sounds really unfortunate that the table won't show up in the SQL Analytics endpoint and semantic model when it's written to Lakehouse after you remove the underscores from the column names using .option(“delta.columnMapping.mode”, “name”).
This is a known limitation mentioned in the official documentation and it is uncertain when Delta Lake interoperability will be extended, you can keep an eye on Microsoft updates for any developments in this area.
You also have the option to make suggestions on Home (microsoft.com).
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@jjaeger94 Please vote and write in the comments https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=a93f4fa7-8d03-ee11-a81c-000d3ae52c8f
https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=a973fa77-03b6-ee11-92bd-00224850a62f
https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=cf1f0082-9250-ef11-b4ac-6045bd8620f1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@jimhav and others, please vote for these ideas (in previous comment) to highlight this need.
(It seems the third link is not working anymore, but the two first ones should be working)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. These are exactly the features I need.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @jjaeger94 ,
It sounds really unfortunate that the table won't show up in the SQL Analytics endpoint and semantic model when it's written to Lakehouse after you remove the underscores from the column names using .option(“delta.columnMapping.mode”, “name”).
This is a known limitation mentioned in the official documentation and it is uncertain when Delta Lake interoperability will be extended, you can keep an eye on Microsoft updates for any developments in this area.
You also have the option to make suggestions on Home (microsoft.com).
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
this is not really a solution. this should not be an issue. when is microsoft planning to fix this?

Helpful resources
Subject | Author | Posted | |
---|---|---|---|
12-06-2024 10:54 AM | |||
11-29-2023 05:58 PM | |||
03-19-2025 05:57 PM | |||
02-18-2025 06:57 AM | |||
03-04-2025 08:26 AM |
User | Count |
---|---|
24 | |
17 | |
8 | |
8 | |
2 |
User | Count |
---|---|
32 | |
24 | |
22 | |
16 | |
12 |