yuribogomolov opened a new issue, #32535: URL: https://github.com/apache/superset/issues/32535
### Bug description We have a dashboard with multiple timestamp columns in a single dataset (e.g., `ts_utc` and `ts_pst`) and want to let users switch between these columns using the time column filter. <img width="572" alt="Image" src="https://github.com/user-attachments/assets/27c016b7-22de-425d-8e1b-6b04a348c65e"; /> ### Expected Behavior When the user selects a different timestamp column (e.g., switching from `ts_utc` to `ts_pst`), Superset should use that column as the time dimension. We’ve confirmed that the underlying query does indeed switch to `ts_pst`. <img width="1504" alt="Image" src="https://github.com/user-attachments/assets/d4705a29-923b-48b1-b034-a4b679c43060"; /> ### Actual Behavior Despite the query showing the correct timestamp column, the chart appears to mix or merge all data together incorrectly, rather than reflecting the new time dimension as expected. <img width="1475" alt="Image" src="https://github.com/user-attachments/assets/c11e392a-822c-49ca-b269-bbc1fb506458"; /> ### Screenshots/recordings _No response_ ### Superset version 4.1.1 ### Python version 3.11 ### Node version 16 ### Browser Chrome ### Additional context The "View as Table" view of the chart gives correct output. This suggests that the issue is specific to the chart visualization rather than the underlying data or query. <img width="690" alt="Image" src="https://github.com/user-attachments/assets/bde20066-f868-41ba-8f4d-feb1eaeec53f"; /> ### Checklist - [x] I have searched Superset docs and Slack and didn't find a solution to my problem. - [x] I have searched the GitHub issue tracker and didn't find a similar bug report. - [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
