SiteMaxCpc and ProxySiteMaxCpc have been removed from the v201206, do check the release-notes here<https://developers.google.com/adwords/api/docs/reference/#v201206>. Oct 26 onwards this'll be the only API available, thus you should not have these fields in selectors.
-bhavin On Saturday, 15 September 2012 01:50:01 UTC+5:30, HK wrote: > > 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 to > obtain all ad groups for a campaign id. SiteMaxCpc and ProxySiteMaxCpc have > been part of the selector for quite a while and always worked fine up until > yesterday. > > System.Web.Services.Protocols.SoapException: > Message: [SelectorError.INVALID_FIELD_NAME @ serviceSelector; > trigger:'SiteMaxCpc', SelectorError.INVALID_FIELD_NAME @ serviceSelector; > trigger:'ProxySiteMaxCpc'] > > This is breaking our sync for a large number of merchants, so a speedy > reply would be much appricated. > > Thanks, > Hans > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
