Alternatives to ConvertToTimezone

[therealdees]

Hi!

I have this dashboard that is used to fire some reports by e-mail and it comes a time of the day that Qlik's server doesn't match my country's time and I get wrong outputs.

I got around it using ConvertToLocalTime(UTC(), 'UTC-03:00') in my expressions, but it seems this function is constantly updated and it glitches my app, specially the scrolling bars.

I'm actually surprised we can't set out timezones in the management console and I assume it's something on the roadmap. Meanwhile, is there a workaround that won't use that much processing?

If I add the value to a variable on script level and then calculate the variable inside my expressions, will it result in the same behavior as using them directly?

[TcnCunha_M · Accepted solution]

what I could suggest is to create a table on that data model, with the timezones you need then use that particular field and use in your report base by with country you are sending.

[marcus_sommer]

Maybe now() is an alternatively for utc() as it provides a time_mode paramter:

now - script and chart function | Qlik Cloud Help

[therealdees]

Hi, it seems to be a good idea, will sure have a try. Thanks for replying.

[therealdees]

Hi, Marcus

Thanks for the reply.

Wouldn't Now() have the same behavior of being constantly recalculated?

[marcus_sommer · Accepted solution]

Not by choosing 0 or 2 as timer_mode:

Argument	Description
timer_mode	Can have the following values: 0 (time at last finished data load) 1 (time at function call) 2 (time when the app was opened)

[therealdees]

This will definitely work!! Thank you very much @marcus_sommer.