Alexander Polyankin
Alexander Polyankin
The order of the columns in models is currently implemented (incorrectly) as a viz setting. It doesn't affect anything outside of the model query itself.
Duplicate of https://github.com/metabase/metabase/issues/38523
I don't think we can do anything here. To confirm and close
This is more like a new feature. I don't understand who it should work/look in the UI.
Given that > if no breakouts specified we should just generate the aggregation without offset The fix is on the BE only.
The BE needs to add an option to `Lib.visibleColumns` to return hidden columns. Only then the FE could use it.
Seems like a duplicate of https://github.com/metabase/metabase/issues/47940
what's happening is that there is a FK in the main table which points to another table; the name of the FK without the ID suffix matches the joined model,...
The reason why we use the FK name for implicit joins is that there can be multiple FKs to the same table, like `owner_id`, `creator_id` etc so you would get...
@alxnddr and one more thing - I think I'd prefer to not use the context here ideally, but up to you