jose-l-goncalves-alb opened a new issue, #31446:
URL: https://github.com/apache/superset/issues/31446
### Bug description
At superset 3.1.3 time_grain variable (sql templating) has correct value,
ex.: PT1M or P1D, accordingly the value chosen from a Time Grain filter.
At superset 4.1.1 time_grain variable (sql templating) has always **None**
value, no matter the value chosen from a time grain filter that I have at
dashboard.
Something changed from 3.1.3 to 4.1.1 version and is not working.
We use this variable, time_grain, to decide which table we use at data set
(we have *_hour/day/month tables with distinct aggregation time). **This
feature is very important to us.**
### Screenshots/recordings
_No response_
### Superset version
4.1.1
### Python version
3.10
### Node version
Not applicable
### Browser
Chrome
### Additional context
FEATURE_FLAGS = {
"ALERT_REPORTS": True,
"ENABLE_TEMPLATE_PROCESSING": True,
"ENABLE_ADVANCED_DATA_TYPES": True,
"ALLOW_FULL_CSV_EXPORT": True,
"HORIZONTAL_FILTER_BAR": True,
"DRILL_TO_DETAIL": False,
"DRILL_BY": False
}
### 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]
