Alexander Polyankin

The issue with hidden joined tables is the same as https://github.com/metabase/metabase/issues/37753 and https://github.com/metabase/metabase/issues/37751 and will be fixed by making the query readonly in such cases. As for the main issue...

^ Likely MySQL enum.

The problem is that the FE checks for `string`, e.g. `type/Text` in the expression parser config https://github.com/metabase/metabase/blob/3b3dcd8647ef7afa8723323297ab5c825e6aedd8/frontend/src/metabase-lib/v1/expressions/config.ts#L127. Each `string` should be changed to `expression` to avoid FE typechecking. And `Lib.diagnoseExpression`...

There is nothing we can do to fix this on the FE now. When metadata from endpoints become correct, we need to check if this is solved completely or some...

This is a large problem. `result_metadata` of dependent cards is not updated in this case.

The problem is that currently the "Exclude" expressions relies on temporal bucketing which is not shown in the expression editor. Apart from that, the expression is weird and hard to...

So that problem is that `zoom` drill is returned in this case for both columns - `ID` and `Product -> ID` that comes from a join. They both have `type/PK`...

Simple change but needs product confirmation

This is intentional behavior. We explicitly don't want to show breakouts in the summarize sidebar until metrics are chosen.

Based on the issue it should be this https://github.com/metabase/metabase/blob/fb4b8ca2a60fede819fff9362956941ccccadbcb/frontend/src/metabase-lib/v1/expressions/format.ts#L102 - i.e. where we cannot find the column by the field ref stored in the expression.