In most cases, customizers/administrators leave the Date & Time field as Local without paying much attention to detail.
With involvement of time, there are 2 behaviors while creating the field (or changing them, but there’s a catch)
You can change from Local to Time-Zone Independent any time, but can’t change from Time-Zone Independent to User Local once saved this way.
User Local
The Date &…
Continue Reading priyeshwagh777’s Article on their blog
Date and Time field’s Time-Zone behavior in D365
In most cases, customizers/administrators leave the Date & Time field as Local without paying much attention to detail. With involvement of time, there are 2 behaviors while creating the field (or changing them, but there’s a catch) You can change from Local to Time-Zone Independent any time, but can’t change from Time-Zone Independent to User Local once saved this way.
Blog Syndicated with priyeshwagh777’s Permission
More About This Author
Array
Dyn365CE15 July 2024Create a Custom Connector For Power Automate & Power Apps
Dyn365CE14 July 2024HTTP Trigger Azure Function Authorization Types simplified | D365 Demystified
Dyn365CE10 July 2024Create your first custom Copilot for Customer Service Hub – Part 2 | Authentication
Dyn365CE8 July 2024Create your first custom Copilot for Customer Service Hub – Part 1
