Thanks. It looks like I used AM instead of PM for the date in my first example...so that example wasn't valid. I can't recreate the issue now when using the correct date: using "20110630 131132 -07:00" gives me the criteria change. I'm not sure why I didn't get the change back on 6/30 and I can't provide a SOAP request to show it right now. I'll have to wait for this issue to happen again and post a valid SOAP request next time. Thanks for the helpful feedback though! :-)
On Jul 12, 11:04 am, jstedman <[email protected]> wrote: > Yeah, that is a very good point. > > I just noticed something about your request that might be causing your > issue: > > <dateTimeRange> > <min xmlns="https://adwords.google.com/api/adwords/cm/ > v201008">20110630 110309 -07:00</min> > <max xmlns="https://adwords.google.com/api/adwords/cm/ > v201008">20110630 011132 -07:00</max> > </dateTimeRange> > > Since the time is listed in 24 hour notation your max time actually > occurs before your min time. > > Try using 13 for the hour on your max time. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
