Formatted Table Reversing Causes Errors

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.