While regressions testing our Google codebase, the vast majority of which we assumed, based on the blogspot notes and release notes, we would not have to touch for the upgrade from v201101 to v201109, we have instead seen that most of our calls now fail. I assume this is what is cryptically meant by 'XML validation for API calls is turned on in production starting with v201109'.
Now we all work for marketing companies, so I assume we're all familiar with spin. But this is stretching things even for present company. In release notes designed for developers who have to track your changes, you should have said something more along the lines of: "we have changed our SOAP parser so that the order of elements in each request is now significant" This would be highlighted, and even be rendered in some of that annoying early-90s scrolling text. This would then make us realise, early on, that we need to budget more time for this upgrade. This is not the first of my posts along these lines recently, and it doesn't go unnoticed that this change, and others ( all the reporting changes, including the requirement of tokens in the HTTP GET, partial deprecation of the ReportDefinitionService ) are changes that provide no benefit to us, are poorly communicated, and not particularly well received by developers ( I note the number of times you've already changed the rollout of the developer token changes for downloading reports ). -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
