BJ Freeman wrote: > > if you got that far it should be all four time fields. > however I don't see the need even with sync to do this.
huh? > > ========================= > BJ Freeman > http://bjfreeman.elance.com > Strategic Power Office with Supplier Automation > <http://www.businessesnetwork.com/automation/viewforum.php?f=52> > Specialtymarket.com <http://www.specialtymarket.com/> > > Systems Integrator-- Glad to Assist > > Chat Y! messenger: bjfr33man > Linkedin > <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> > > > > Adam Heath sent the following on 6/16/2010 1:34 PM: >> Any place that specifies a date in a seed xml *must* also specify a >> timezone. If you do an install on one machine, then do a >> dump/copy/import on another machine, that is in a different timezone, >> then reimport the original seed xml, the timestamps will not match. >> >> What happens, is that there is no timezone on the fromDate fields. >> The original import uses the timezone of the local machine as the >> default in this case. >> >> When the seed xml is reimported on the second machine, it uses the >> default timezone of the second machine. If the timezones are >> different, then the fromDate will be different as well, and you'll get >> duplicate records in the database. >> >> The fix here is to update all the seed xml files to specify a >> timezone. Probably using UTC would be the sensible approach. >> >
