I noticed that when load leads in to vicidial, the gmt_offset_now is 1 less than the actual GMT of the area. i.e. area code 954 which is GMT (-5) has a gmt_offset_value of -4. Is this correct?
If this is correct, then what happens in 6 months when we are not in DST, will the system autocorrect?
gmt_offset_now Questions
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
6 posts
• Page 1 of 1
gmt_offset_now Questions
by scottgutman » Tue Jun 16, 2009 8:48 am
- scottgutman
- Posts: 75
- Joined: Mon Mar 23, 2009 4:17 pm
by mflorell » Tue Jun 16, 2009 8:56 am
The GMT offset now field is the current offset from Zulu(or Greenwich Mean) Time, not the timezone of the lead. Yes it does auto-adjust according to the area-code that you are in, and it checks it every night.
- mflorell
- Site Admin
- Posts: 18387
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
by scottgutman » Tue Jun 16, 2009 9:28 am
what what should the gmt_offset_now field be for New York?
- scottgutman
- Posts: 75
- Joined: Mon Mar 23, 2009 4:17 pm
by scottgutman » Tue Jun 16, 2009 12:01 pm
so now that we are in DST, the gmt_offset_now is -4, and after november it will be -5.
is there a script that corrects all the leads in the table?
or does the vicidial internally calculate when the lead was inserted to adjust for times when we are not in DST?
is there a script that corrects all the leads in the table?
or does the vicidial internally calculate when the lead was inserted to adjust for times when we are not in DST?
- scottgutman
- Posts: 75
- Joined: Mon Mar 23, 2009 4:17 pm
6 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 61 guests