Incorrect Namespaces in Google.Api.Ads.AdWords.v201506.ReportDefinition

222 views
Skip to first unread message

Dan Kearney

unread,
Jul 1, 2015, 9:04:02 AM7/1/15
to adwor...@googlegroups.com
Just to let you all know that if you go to use the new Sample .NET code for the v201506 Reporting you will first need to go to Google.Api.Ads.AdWords.v201506.ReportDefinition and fix the XmlTypeAttribute NameSpace. 

They are still pointing to the v201502 versions so the code will not execute correctly.

Might save some of you a headache or two.



 

Bejan @ MarketFlare

unread,
Jul 1, 2015, 6:02:57 PM7/1/15
to adwor...@googlegroups.com
Hello Dan and thanks for your help.

I'm pulling the lastest .NET AdWords dll from Nuget. Will there by a version update there soon or should I fix the namespace issues from code at the github source and compile?

After updating from v201502 to v201506 I get the following exception from GetResponse():

ReportDownloadError.INVALID_REPORT_DEFINITION_XML, Trigger: Invalid ReportDefinition Xml: cvc-complex-type.2.4.a: Invalid content was found starting with element 'selector'. One of '{"https://adwords.google.com/api/adwords/cm/v201506":id, "https://adwords.google.com/api/adwords/cm/v201506":selector}' is expected.

Umesh Dengale

unread,
Jul 1, 2015, 6:18:49 PM7/1/15
to adwor...@googlegroups.com, dannyk...@gmail.com
Hello,

Thanks for pointing out above issue. We have filed issue and engineers from the .Net client library team will look into it.

Thanks,
Umesh, AdWords API Team.

Matt Akers

unread,
Jul 6, 2015, 3:03:04 PM7/6/15
to adwor...@googlegroups.com, dannyk...@gmail.com
Looks like Line 35, 175, and 195 are the offending lines in the ReportDefinition.cs file.  

Umesh Dengale

unread,
Jul 6, 2015, 3:41:49 PM7/6/15
to adwor...@googlegroups.com, matt.a...@gmail.com, dannyk...@gmail.com
Hello,

Thanks for pointing out the line numbers. We have filed an issue and our engineers are working on a fix.

Nadine Sundquist (AdWords API Team)

unread,
Aug 6, 2015, 4:16:31 PM8/6/15
to AdWords API Forum, matt.a...@gmail.com, dannyk...@gmail.com
Hello Dan, Bejan, and Matt,

The fix is available. Hopefully, you've already picked it up. Thanks again for being so helpful in reporting this. 

Cheers,
Nadine, AdWords API Team
Reply all
Reply to author
Forward
Message has been deleted
0 new messages