SO your Azure webapp may assume GMT, so the umbraco forms entries are entered with a GMT datetime as the submitted date instead of whatever your local timezone is.
This can be confusing to end-users as they will not generally know what GMT is or recognise it by just looking at it.
The solution here is to use the extremely long-winded timezone identifiers MS uses for Azure.
On your webapp go to configuration, from there look for WEBSITE-TIME-ZONE(using underscores instead of hyphens) in the list of settings. if it is not present, add a new one and enter your stupid timezone indentification into the value.
Umbraco Forms submission date in azure
SO your Azure webapp may assume GMT, so the umbraco forms entries are entered with a GMT datetime as the submitted date instead of whatever your local timezone is.
This can be confusing to end-users as they will not generally know what GMT is or recognise it by just looking at it.
The solution here is to use the extremely long-winded timezone identifiers MS uses for Azure.
On your webapp go to configuration, from there look for WEBSITE-TIME-ZONE (using underscores instead of hyphens) in the list of settings. if it is not present, add a new one and enter your stupid timezone indentification into the value.
You can find a list here: https://sajeetharan.com/2019/11/12/how-to-set-timezone-in-azure-app-service/
So to give an example if I wanted to use AEST I would have to enter "AUS Eastern Standard Time"
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.