Forum Discussion
Formatted Table Reversing Causes Errors
Hi all,
Using PBID April, 2026
I formatted a table so that the name was in Bold followed by an emoji to make it easier to find the table in a sea of tables.
I then tried to rename it back to the original name with plain text.
That's when the errors started on refresh:
Container exited unexpectedly with code 0x80131623. PID: 33556. Used features: (none).
and
Error Message:
Container exited unexpectedly with code 0x80131623. PID: 37704.
Used features: Adbc.DataSource/ADBC Driver Foundry Driver for Snowflake/unknown-dirty/Snowflake/nn.nn.nnn.
How can I rename the table with plain text and defeat the errors?
Thanks,
w
Hi tecumseh
I would not assume that the emoji itself is the root cause.
A table/query name with an emoji or bold Unicode characters is not ideal, and I would avoid it in model/query names, but the error you are getting looks more like a Power Query/Mashup container crash during refresh. The important part is this:
Used features: Adbc.DataSource / ADBC Driver Foundry Driver for Snowflake
That points much more strongly to the Snowflake ADBC connector path than to a simple table rename issue. If the rename had only broken a reference, I would normally expect an expression/reference error, not a container crash.
I would try this in a copy of the PBIX:
First, manually retype the table/query name using plain text only. Do not copy/paste the old name, because there may be hidden Unicode characters left from the formatted name.
Then open Power Query and check the Advanced Editor for that query and any dependent queries. Look for references to the old name, especially names wrapped like `#"Old Query Name"`.
Also check whether other queries, calculated tables, relationships, measures, or visuals still reference the formatted/old table name.
If the model still fails on refresh, I would test the Snowflake connector implementation rather than focusing only on the emoji. In the Source step, check whether the Snowflake connection uses something like:
`Implementation="2.0"`
If it does, try removing that flag and refreshing again, so the connection can use the older ODBC implementation where applicable. Also clear the data source permissions/cache for the Snowflake source and reconnect.
If removing the ADBC implementation fixes the issue, then the rename probably only triggered/exposed the problem, but the real issue is likely related to the Snowflake ADBC connector or the April 2026 Desktop build.
I would also test the same PBIX in the latest Power BI Desktop version, or in a previous version if possible. If the issue reproduces only with the ADBC Snowflake implementation, I would open a support ticket and include the Mashup logs, because this looks more like a connector/container crash than a normal modeling rename problem.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
3 Replies
Hi tecumseh
I would not assume that the emoji itself is the root cause.
A table/query name with an emoji or bold Unicode characters is not ideal, and I would avoid it in model/query names, but the error you are getting looks more like a Power Query/Mashup container crash during refresh. The important part is this:
Used features: Adbc.DataSource / ADBC Driver Foundry Driver for Snowflake
That points much more strongly to the Snowflake ADBC connector path than to a simple table rename issue. If the rename had only broken a reference, I would normally expect an expression/reference error, not a container crash.
I would try this in a copy of the PBIX:
First, manually retype the table/query name using plain text only. Do not copy/paste the old name, because there may be hidden Unicode characters left from the formatted name.
Then open Power Query and check the Advanced Editor for that query and any dependent queries. Look for references to the old name, especially names wrapped like `#"Old Query Name"`.
Also check whether other queries, calculated tables, relationships, measures, or visuals still reference the formatted/old table name.
If the model still fails on refresh, I would test the Snowflake connector implementation rather than focusing only on the emoji. In the Source step, check whether the Snowflake connection uses something like:
`Implementation="2.0"`
If it does, try removing that flag and refreshing again, so the connection can use the older ODBC implementation where applicable. Also clear the data source permissions/cache for the Snowflake source and reconnect.
If removing the ADBC implementation fixes the issue, then the rename probably only triggered/exposed the problem, but the real issue is likely related to the Snowflake ADBC connector or the April 2026 Desktop build.
I would also test the same PBIX in the latest Power BI Desktop version, or in a previous version if possible. If the issue reproduces only with the ADBC Snowflake implementation, I would open a support ticket and include the Mashup logs, because this looks more like a connector/container crash than a normal modeling rename problem.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi tecumseh,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to Ritaf1983 for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community
Hi tecumseh ,
May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions. Your update will be valuable to the community and may assist others with similar concerns.
Thank you.
