Understanding TimeZoneOffset
Here’s what you need to know to understand the TimeZoneOffset field in SmartConnect.
For the purpose of this example, we are going to refer to SmartConnect 21 On-Premise. Just to clarify, the offset value is not displayed directly in the SmartConnect UI. If you’re looking at the ScheduleMaster SQL table, then it makes sense to be showing up that way. For SmartConnect.com, we used to handle the TimeZoneOffset value on our side (since it’s a cloud version), using the same logic as we did for SmartConnect 21.
The TimeZoneOffset indicates how much a particular time zone differs from Coordinated Universal Time (UTC).
Let me explain with a quick example:
If the server or machine running the eOne Windows Service is set to Central Time, then the same time zone should also be selected in SmartConnect >> File >> Maintenance >> Setup (recommended).
If you want to schedule a job in Central Time (which is typically preferred based on how your business operates), then that same time zone should be selected in SmartConnect >> System >> Settings (recommended).
I’d like to schedule a job to run at 6:30 AM Central Time.
Please Note:
- The SmartConnect UI displays the date and time in Central Time (or your local time zone), but the scheduler runs based on the timezone offset defined in Settings >> Setup.
- For SC21 on-premises, the SmartConnect database always stores the date/time in UTC.
Have a question? Please reach out to us at support@eonesolutions.com
