-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 use segments in case function for custom columns value #24922
Labels
Administration/Metrics & Segments
.Frontend
Priority:P2
Average run of the mill bug
Querying/Notebook/Custom Column
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Milestone
Comments
flamber
added
Priority:P2
Average run of the mill bug
Administration/Metrics & Segments
.Frontend
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
Querying/Notebook/Custom Column
and removed
.Needs Triage
labels
Aug 22, 2022
Regression since 0.43.0, likely by #21342 |
1 task
This was referenced Oct 11, 2023
This was referenced Oct 24, 2023
Merged
This was referenced Feb 5, 2024
Merged
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Administration/Metrics & Segments
.Frontend
Priority:P2
Average run of the mill bug
Querying/Notebook/Custom Column
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Describe the bug
Hi there,
I have a custom column created with an older version of Metabase using a case function. After upgrading it seems like if I try to edit it normalizes the value to some invalid format and I can no longer query the data.
This is the value that it works -> https://vertis.d.pr/ouisBv
Once I edit something, it gets transformed into https://vertis.d.pr/lnwzfe which is invalid, giving this error https://vertis.d.pr/6uox2m
I have to mention that all values are Segment names, not columns.
Logs
To Reproduce
Steps to reproduce the behavior:
case([Segment name],'Segment','Others')
case([Segment name] = True,'Segment','Others')
which breaks the query.Expected behavior
The normalization should not break the query.
Screenshots
Information about your Metabase Installation:
You can get this information by going to Admin -> Troubleshooting.
Severity
The bug is blocking me from editing any query which uses segments in custom columns.
The text was updated successfully, but these errors were encountered: