Is your feature request related to a problem? Please describe.
Customers naturally want to use their preferred time zone (usually where they are located), but we have difficulty ensuring that across the board.
In Azure Cloud, the SQL Server has to be UTC, but the VM can be whatever time zone we want.
Describe the solution you'd like
We'd like for the data in the DB to be UTC and the API/ViewModels to expose it in the Server's time zone accurately (and/or in UTC as well), so that can get it more accurately in both the webapi's and templates
Describe alternatives you've considered
We considered customizing templates to show the user's desired time zone - but that makes it harder to relate with the backend on lists, auditing and logs
We tend to hide the time (only show date), but depending on when something happens (i.e. order placed), it shows up as "the next day" for the user, which is confusing
We also end up appending "GMT" to every date, but it's not something some users relate to.
Additional context
This topic was discussed with Jeppe at the Summit
Is your feature request related to a problem? Please describe. Customers naturally want to use their preferred time zone (usually where they are located), but we have difficulty ensuring that across the board. In Azure Cloud, the SQL Server has to be UTC, but the VM can be whatever time zone we want.
Describe the solution you'd like We'd like for the data in the DB to be UTC and the API/ViewModels to expose it in the Server's time zone accurately (and/or in UTC as well), so that can get it more accurately in both the webapi's and templates
Describe alternatives you've considered
Additional context This topic was discussed with Jeppe at the Summit