-
Notifications
You must be signed in to change notification settings - Fork 13.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
Drill-to-detail not update the underlying data #30952
Comments
Hey @rithysokun! 👋 I'm here to help you with any bugs, questions, or contributions you have for Superset. Let's tackle this together! The issue you're experiencing with the 'drill-to-detail' feature not updating the underlying data in Superset version 3.0.0 could be due to several conditions under which this feature fails to function correctly:
Ensure that these conditions are met in your setup. If the issue persists despite meeting these conditions, it might be a bug specific to your environment or configuration. |
@dosu all the above conditions are met in my context . Are there anything to fix? |
If all the conditions mentioned are met and the issue persists, it might be helpful to check the following:
If none of these steps resolve the issue, it might be worth considering if there are any environment-specific factors or custom configurations that could be influencing the behavior. |
Bug description
In version 3.0.0 . I click feature drill-to-detail behind the pie chart but the chart does not render and update the data in the table when using the drill-to-detail .
However, when click edit chart -> sample -> the data is updated just the same as result in sql lab .
Is this a bug in Superset version 3.0.0?
Screenshots/recordings
qcom2.mov
Superset version
3.1.3
Python version
3.9
Node version
16
Browser
Chrome
Additional context
Expected behaviour
The result from "drill-to-detail" feature should be the same as the result of the query shown in SQL lab . Store ID : 176 is missing in the "drill-to-detail" table
Checklist
The text was updated successfully, but these errors were encountered: