AdWords API Re: API Service Bug - Dijkstra - com.googlegroups.adwords-api

5 messages in com.googlegroups.adwords-apiAdWords API Re: API Service Bug

From	Sent On	Attachments
AdWords API Advisor	24 Jul 2008 11:01
Dijkstra	24 Jul 2008 14:57
AdWords API Advisor	25 Jul 2008 08:34
Dijkstra	27 Jul 2008 15:50
AdWords API Advisor	28 Jul 2008 08:47

Subject:	AdWords API Re: API Service Bug
From:	Dijkstra (pepi...@gmail.com)
Date:	07/24/2008 02:57:55 PM
List:	com.googlegroups.adwords-api

Hi Jeff,

On 24 jul, 20:02, AdWords API Advisor <adwo...@google.com> wrote:

I'll see what the engineering team has to say about this as I'm assuming there was some initial rationale (though it may now seem misguided) to impose that sort of positional behavior. Just to set expectations, I'd think that it's more likely that we'd see this officially documented in the developer's guide rather than the underlying behavior changing completely, because the API has been around for some time now and there very well may be folks who are unwittingly relying on the behavior, and we try to minimize breaking changes in between API releases.

Thanks for your quick reply! Yes, this makes sense, but the correct fix will be binding the parameters name correctly. I mean, getting the "endDate" value from the parameter named "endDate" and not using the positional appereance. Parameters name must be checked trowing a Fault also.

Given that this is such an evident error and if no developer reported it earlier is an indication of A) everyone sends the parameters in the expected order or B) "getAdGroupStats" is barely used. Please, note that I can't change my SOAP library without a huge efford nor I can't change the way parameters are serialized. I think many developers may be in the very same situation.