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.
I guess given the documentation, with any converted timestamp I would expect to see the offset from UTC, similar to (see below in red), any timestamps after the first have been converted from UTC to something else, so they must carry an offset from UTC.
Hi DanielAmbler ,
If you observe carefully, you can notice the time difference already added to it (i.e. 1 hr, 10:24 --> 11:24)
{
"name": "var_utcnow",
"value": "2024-06-13T10:24:21.7790903Z"
}
{
"name": "var_utc_convert_timezone_1",
"value": "2024-06-13T11:24:21.7790903Z"
}
But if you are talking about representation or formating of the time, please share this in feedback. At present this is by design.
However, your suggestion is definitely valuable! We use customer feedback like yours to improve the product. The more users who request the ability to customize backgrounds, the higher it moves on our list.
Appreciate if you could share the feedback on our Microsoft Fabric Ideas. Which would be open for the user community to upvote & comment on. This allows our product teams to look into your feedback and improve the product.
Hope this is helpful. Please do let me know incase of further queries.