Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Carl-Johan, This issue has been fixed in API version v201607. The BatchJobOps.xsd has been removed. Please use BatchJobOpsService.wsdl instead

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Carl-Johan, This issue has been fixed and the responses should now match the wsdl for BatchJobService. Please rerun any operations which you were unable to perform earlier and let us know if you encounter any issues. Regards, Shwetha, AdWords API Team. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Carl-Johan, The engineering team is still investigating the issue. We don't have an update at the moment. You could try to generate the code using this schema for now as an alternative to BatchJobOps.xsd. Let me know if

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

No news yet? On Thursday, June 9, 2016 at 6:58:43 AM UTC+2, Joyce Lava wrote: > > Hi Carl-Johan, > > As of the moment, there is no news yet. But I assure that will let you > know as soon as possible if there is any update. Will try to check on them > again by Friday. > > Thanks and Regards, > Jo

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Carl-Johan, As of the moment, there is no news yet. But I assure that will let you know as soon as possible if there is any update. Will try to check on them again by Friday. Thanks and Regards, Joyce, AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Carl-Johan, The engineering team is actively investigating on the issue. Let me check with them about any updates they can provide as of the moment. Thanks and Regards, Joyce, AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: http

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Any updates? Can the engineering team confirm the problems we have been having? /cjk On Friday, June 3, 2016 at 8:13:20 PM UTC+2, Joyce Lava wrote: > > Hi Carl-Johan, > > The engineering team is looking into the issue. If there is any update, we > will inform you as soon as possible. > > Regard

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Carl-Johan, The engineering team is looking into the issue. If there is any update, we will inform you as soon as possible. Regards, Joyce, AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Excellent to hear! But given that the sunset for v201509 is in a few weeks, I think I have to implement a simple xml-parser that doesn't validate what we receive just so we can move up to v201603 before the deadline. Any hints on which direction you are leaning toward for a fix would be much ap

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Carl-Johan, Sorry for the delayed response. The engineering team is working on this issue. We will let you know about any updates once available. Thanks and Regards, Joyce, AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https:/

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

How is it going? Haven't heard from any of you for a few days. Have your tried diffing the v201509 and later XSDs? On Friday, June 3, 2016 at 1:37:34 AM UTC+2, Carl-Johan Kjellander wrote: > > We verified today that sending XML using the BatchJobOps.xsd works, the > none of the replies actually

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

We verified today that sending XML using the BatchJobOps.xsd works, the none of the replies actually validates. All the new xsds from v201601 and onward has everything sorted alphabetically instead of using the old structure that has evolved over time adding stuff to the end of every sequence.

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

https://developers.google.com/adwords/api/docs/guides/batch-jobs#supported_operations is where we found the links btw. At the time I started messing with it it was v201603 and v201605, but the same problem applies to the latter xsd, it has moved around the fields in ApiError. On Wednesday, Jun

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

I found it here: https://adwords.google.com/api/adwords/cm/xsd/v201603/BatchJobOps.xsd The v201509 version of that xsd was linked from a migration guide that we followed. I suggest doing a diff between the xsd above and this one: https://adwords.google.com/api/adwords/cm/xsd/v201509/BatchJobOp

Re: BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

Hi Cal-Johan, I am not sure on where did you find the XSD for v201603, but upon checking on the BatchJobService wsdl, it shows the part: The API error base class that provides details about an error that

BatchJobService mutateResponse says it uses v201603 but the response seems to be v201509

I am doing a new integration to the v201603 API and implementing what we need for the BatchJobService. However, I made a mistake and downloaded the mutateResponse and started trying to parse the XML but our parser only spat out errors, specifically on errorString. This is the message I got fro