I did >>
https://groups.google.com/d/msg/adwords-api/h6ooQ9rcGAA/ph3-Fd2ICgAJ
Thanks for the super quick response!
-Steve
*--*
Steve Rohde
Product Management | Acquisio
Tel: 450.465.2631 ext. 223
Email: sro...@acquisio.com
Follow Us:
Twitter: http://twitter.com/acquisio
LinkedIn: http
Hi Steve,
Since this is an old issue, can you please open a new thread and explain
the issue that you are facing?
Regards,
Vishal, AdWords API Team
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://p
Reed, I'm running into exactly the same issue you described. How did you
resolve it?
Thanks,
Steve
On Monday, January 23, 2012 at 2:50:32 PM UTC-5, Reed wrote:
>
> Arrgh. never mind, forgot about the strict XML validation re order of
> the elements. WSDL confuses soapUI - it doesn't even sh
Arrgh. never mind, forgot about the strict XML validation re order of
the elements. WSDL confuses soapUI - it doesn't even show all of the
SOAP elements.
thanks,
-reed
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.
Working on updating more v2009 code to v201109, am building my own XML
request but using the AddTextAds.php example as a guide. Sending the
following SOAP message:
http://schemas.xmlsoap.org/soap/
envelope/" xmlns:v20="https://adwords.google.com/api/adwords/cm/
v201109" xmlns:xsi="http://www.w3.
