Sometimes it’s ridiculously trivial bugs that get in the way of implementing great functionality. Luckily, sometimes they get fixed. Gustaf “Surströmming” Westerlund reports from the field.
In earlier versions of CRM (I have tested it in CRM 2013 SP1) if you added a whole number field on appointment and formatted it as a timezone, you could no longer create any appointments without getting a crash.
I just tested CRM 2016 Update 1 and this works great now, so if you want to build logic that mimics the timezone behavior of Outlook (with syncing timezone of course, since that isn’t done), that can now be done. Also easier with the new timezone independent datetime fields.