The server hosting my Dundas BI instance has UTC Timezone. The Default Timezone in application config is set to UTC. The user’s dundas session timezone(dundas.context.currentSession.timeZoneId) is UTC. The user’s computer’s timezone is in CST. When using a calendar range and selecting “Today” token, the date selected is of a UTC “Today”. This is to be expected as the settings are laid out.
If I change the user’s dundas session timezone(dundas.context.currentSession.timeZoneId) to CST by setting the user’s timezone and then make sure dundas.context.currentSession.timeZoneId = “Central Standard Time” on the dashboard, the “Today” token still returns UTC “Today”.
I am now confused as to what controls the timezone of a token selector. I do not seem to be able to get the token to use a local timezone no matter what I do. This is crucial as users need to be able to control the dashboards in their timezone.