Re: Calling get on AdGroupService fails with INVALID_FIELD_NAME for 'SiteMaxCpc' and 'ProxySiteMaxCpc'

2012-09-17 Thread HK
Thanks for pointing this out, bhavin, I had missed the fact that these had been retired (was looking at the wrong version). Hopefully they will be available until 10/26 at least as it'll take us a little while to get this corrected in our production environment. Hans On Sunday, September 16, 2

Re: Calling get on AdGroupService fails with INVALID_FIELD_NAME for 'SiteMaxCpc' and 'ProxySiteMaxCpc'

2012-09-16 Thread bhavin
SiteMaxCpc and ProxySiteMaxCpc have been removed from the v201206, do check the release-notes here. Oct 26 onwards this'll be the only API available, thus you should not have these fields in selectors. -bhavin On Saturday, 1

Re: Calling get on AdGroupService fails with INVALID_FIELD_NAME for 'SiteMaxCpc' and 'ProxySiteMaxCpc'

2012-09-14 Thread HK
Good news, looks like this now has stopped. Don't see any errors past noon today and I am not able to repro this with two accounts that were previously experiencing this. Hans On Friday, September 14, 2012 1:20:01 PM UTC-7, HK wrote: > > Hi, > > Starting at 9/13 4.21 pm PDT we starting seeing t

Calling get on AdGroupService fails with INVALID_FIELD_NAME for 'SiteMaxCpc' and 'ProxySiteMaxCpc'

2012-09-14 Thread HK
Hi, Starting at 9/13 4.21 pm PDT we starting seeing the above error for a lof of our accounts. We have not changed our client code in this area for many many months. Is this a problem on the AdWords side or did the APIs change behavior? We are using v201206, and get this error when calling get