In this article
Please note that timezones in DayBack behave differently depending on the calendar source.
I have team members in different time zones; how does that work in DayBack?
DayBack will translate events into the users' local timezone. So if I have my computer set to the eastern time zone and create an event for 4pm, it will show up as a 1pm event for someone whose computer is set to pacific time.
Add a timezone selector to DayBack
Using a custom app action, you can add a timezone selector to DayBack's left-hand sidebar, making it easy to view the whole calendar in a different timezone. Example code and instructions are here: timezone selector. Go further and learn how to script and enhance timezone support here: enhanced timezone support:
Show timezones on hover
Translate your events into different timezones using a tooltip that's easy to customize. Example code and step-by-step instructions are here: timezone tooltips.
Time zones in Salesforce
There are two time zone settings in Salesforce, one for your org, and one for each user. The org-level setting is just used as a default for the creation of new users: when time zones are actually used it is always the user's time zone that is in effect.
Your device (computer, or mobile device) has its own time zone and, in general, you'll want your device time zone to be the same as the time zone set up for your user in Salesforce. (Of course, each user in the org can have their own time zone--you just want their device and their time zone in Salesforce to be the same for the most predictable results).
How DayBack treats timezones in Salesforce
DayBack respects the user's time zone from Salesforce and, if the user's device time zone is the same, the event will appear at the same time in Salesforce and in DayBack. Under the hood, Salesforce stores times as UTC time and applies an offset depending on the user's time zone setting in Salesforce. DayBack does the same thing, applying an offset using the user's device timezone. So if the user's device time zone and their Salesforce time zone setting are the same, the event will appear at the same time.
Events can appear at different times in DayBack and Salesforce in only two cases:
The user's device timezone differs from that in the user's settings in Salesforce. In this case, DayBack will display the event in the user's device time zone. This can be handy when you're traveling and your mobile device is in your physical time zone: you won't need to log into Salesforce to change your time zone. Just know that when you make new events you'll be making them in the local time zone (the device time zone).
The item in question is a custom object, set to use Date/Time fields (instead of just Date fields), has been marked as an All-Day event, and the user's device timezone differs from that in the user's settings in Salesforce. If all those things are true the event may show up on the day of the device time zone in DayBack since custom objects with Date/Time fields always have times. Note that this is never an issue with custom objects set to Date fields only--just those set to Date/Time fields that match the conditions above.
Time zones in FileMaker
Since FileMaker doesn't have any time zone support, FileMaker records are shown at the literal time entered in an event. So if a FileMaker record has "8:00:00" entered into its start-time field, that record will show up at 8am regardless of what time zone you're in when you look at that event in DayBack. If you require timezone support in your FileMaker setup, please get in touch.