Forum Discussion
Converted timestamps using expression functions always have UTC timezone - is this expected?
- Anonymous2 years ago
Hi DanielAmbler ,
Apologize for the issue you are facing. The best course of action is to open a support ticket and have our support team take a closer look at it: LinkAfter creating a Support ticket please provide the ticket number as it would help us to track for more information.
Hope this helps. Please let us know if you have any other queries.
Hi DanielAmbler ,
Thanks for using Fabric Community.
Can you please explain your query little bit? If possible can you please explain with an example?
If you can provide these details, I can guide you better.
Hi Anonymous ,
Thanks for your reply, sure I can provide more information. Given this test pipeline
The first activity sets a timestamp (@utcnow())
The second converts from utc (
- Anonymous2 years agoNot applicable
Hi DanielAmbler ,
This is an expected behvaiour.
Here are my results when I tried to reproduce your scenario.{ "name": "var_utcnow", "value": "2024-06-13T10:24:21.7790903Z" } { "name": "var_utc_convert_timezone_1", "value": "2024-06-13T11:24:21.7790903Z" } { "name": "var_convert_timezone_1_timezone_2", "value": "2024-06-13T03:24:21.7790903Z" } { "name": "var_formatted", "value": "2024-06-13T03:24:21.7790903Z" }
Can you please help me understand what are you expecting as output here?