-
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
Custom Expression validator too strict when field name is the same as a function #21513
Labels
.Frontend
Priority:P2
Average run of the mill bug
Querying/Notebook/Custom Expression
.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
Type:Bug
Product defects
Priority:P2
Average run of the mill bug
.Frontend
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
Querying/Notebook/Custom Expression
labels
Apr 7, 2022
This was referenced Jan 11, 2024
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
.Frontend
Priority:P2
Average run of the mill bug
Querying/Notebook/Custom Expression
.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
Custom Expression validator does not allow field names that are the same as functions e.g
[Count] * 2
Regression since 0.42
Workaround: For metrics, create a Custom Expression with a custom name (e.g. MyCount). For fields, change the name in the Data Model.
To Reproduce
[Count] * 2
as "CC" - errors withExpecting number but found function Count returning aggregation
Information about your Metabase Installation:
Tested 0.41.6 thru 0.42.3/4 and master
The text was updated successfully, but these errors were encountered: