Suggest an Idea

[mehdibassam]

DTTM fields stored as local date/time fields in tables are changed to show US date/time when loaded into Qlik Sense SaaS and there is no setting or ability to change this. 

It would be very useful to be able to set a time zone in a SaaS tenant.

[AdamJohnson]

Yes please, a lot of people are migrating to SaaS and have local based time and date calculations in their apps. It's not efficient to have to change every single app. If their was a local based timing setting in QMC, this would help. We live in NZ and a lot of people importing their apps find that the date is a day behind. There are work arounds obviously but it is not efficient to have to apply these for every app.

[anderseriksson]

Learned the hard way that the SaaS EU servers run timezone GMT?!?
A SaaS offering I assume the tenant timezone should reflect the customers location
NOT the SaaS hardwares location.
There need to be a timezone setting for the tenant. Should have been from day one!

[veronica1]

Completely Agree. Moreover, not all users are able to go to the script section to modify the variables.

[MichelLalancette]

We are currently migrating to SaaS and this is something we noticed as well.

This is a significant pain considering that many of our calculations use Today() as a reference point.

Even something as simple as the LastReloadDate being incorrect is inconvenient.

There really needs to be a setting for this.

[MaryseC]

I would have loved to know this flaw before migrating.  We were not expecting to have to edit all the load script, bookmarks, etc...  everything where we use today(), now() and such. 
Being able to choose our timezone seemed a no-brainer and never thought that this would become an issue.

[APiccoli]

With a global setting per Tenant or a system Variable per App that set the default Time Zone, customers migrating from Client Manged to Cloud do not need to review the logic of scrip and Visualization objects formula's, allowing a fast and smooth transition.