Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't edit metadata for models with several columns #36364

Open
renatodossantosleal opened this issue Dec 4, 2023 · 3 comments
Open

Can't edit metadata for models with several columns #36364

renatodossantosleal opened this issue Dec 4, 2023 · 3 comments
Labels
.Frontend Priority:P2 Average run of the mill bug Querying/Models aka Datasets .Team/QueryingComponents Type:Bug Product defects

Comments

@renatodossantosleal
Copy link

Describe the bug

When working with models in metabase 0.47.8 I cannot edit metadata on models that have more than 30+ columns.
The behavior is when editing a model (after its creation) we try to click on a column far on the right and what happens is that a column at the beginning of the table is actually selected on the right side (detail side).

Bug first reported in: https://discourse.metabase.com/t/not-able-to-select-specific-columns-in-edit-metadata-when-working-with-model/26059

To Reproduce

  1. Go to a model with 30+ columns and select edit metadata.
  2. Try to edit a column at the end of the table (i.e. column number 40)
  3. See error (column details are from another column, not the one selected)

Expected behavior

No response

Logs

No response

Information about your Metabase installation

- Your browser and its version: Versão 119.0.6045.199 (Versão oficial) 64 bits
- Your operating system: ( Ubuntu 22.04.3 LTS )
- The type of database(s) you've connected to Metabase: (Redshift)
- The version of Metabase you're running: ( 0.47.8 )
- Hosting Env: EKS
- Metabase's internal database type: (Postgres)

Severity

High

Additional context

We cannot work with big models because of this error, preventing us to move to metabase as our solution. (We have 20+ models like this)

@paoliniluis
Copy link
Contributor

Thanks, we'll release v48 in the next few days, can you check if this has been fixed?

@ignacio-mb
Copy link
Contributor

Hi @renatodossantosleal is this still happening in 48?

@mikeflynn
Copy link

I'm still seeing this issue on 0.48.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.Frontend Priority:P2 Average run of the mill bug Querying/Models aka Datasets .Team/QueryingComponents Type:Bug Product defects
Projects
None yet
Development

No branches or pull requests

5 participants