-
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
Only show Object Detail when there is 1 row - otherwise always show Table #13717
Labels
.Correctness
Priority:P2
Average run of the mill bug
Querying/GUI
Query builder catch-all, including simple mode
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Visualization/
Projects
Milestone
Comments
flamber
added
Type:Bug
Product defects
Priority:P2
Average run of the mill bug
Visualization/
.Correctness
Querying/GUI
Query builder catch-all, including simple mode
labels
Nov 6, 2020
nemanjaglumac
added a commit
that referenced
this issue
Nov 12, 2020
nemanjaglumac
added a commit
that referenced
this issue
Nov 13, 2020
38 Product Pod Planning
automation
moved this from 38.1+ Bug Fixes
to Closed Issues and PRs
Sep 23, 2021
Merged
1 task
1 task
This was referenced Jan 11, 2024
This was referenced May 8, 2024
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
.Correctness
Priority:P2
Average run of the mill bug
Querying/GUI
Query builder catch-all, including simple mode
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Visualization/
Describe the bug
When filtering on a field type "Entity Key", but the result might contain more than 1 row (eg. because of composite keys #3475), then an Object View is shown, which leads to incorrect representation of the results.
To Reproduce
Expected behavior
Only show Object Detail, when the result is 1 row - otherwise always show a table.
This will protect against accidental incorrect Field Type, or when the data somehow deviates from expectations.
Information about your Metabase Installation:
Metabase 0.34.3 thru 0.37.0.2 - probably always been the behavior.
Additional context
Related to #7599 and #9447 and #11503
The text was updated successfully, but these errors were encountered: