New PHP Client Lib 8.0.0 is not supporting includezeroimpression for various reports

75 views
Skip to first unread message

Chirag

unread,
Feb 5, 2016, 7:29:29 AM2/5/16
to AdWords API Forum
Hello All,

I was working on moving my code to new PHP Client Lib 8.0.0 and was getting error while downloading campaign performance report.
The same code is working fine with client library 7.0.2

Error was :
"Response Code: 400
Error Message: Report download failed. Underlying errors are 
Type = 'ReportDownloadError.INVALID_REPORT_DEFINITION_XML', Trigger = 'Invalid ReportDefinition Xml: cvc-complex-type.2.4.a: Invalid content was found starting with element 'includeZeroImpressions'. One of '{"https://adwords.google.com/api/adwords/cm/v201506":id, "https://adwords.google.com/api/adwords/cm/v201506":selector}' is expected.', FieldPath = ''. "


Soap Log ; 

Parameters:
__rdxml: <?xml version="1.0" encoding="UTF-8"?>
<reportDefinition><includeZeroImpressions>false</includeZeroImpressions></reportDefinition>

Thanks

Anthony Madrigal

unread,
Feb 5, 2016, 4:18:00 PM2/5/16
to AdWords API Forum
Hi,

Your report definition does not appear to be set up correctly. There are no fields or any indication of the report type. 

You can see how to set it up correctly in this example.

Regards,
Anthony
AdWords API Team

Chirag

unread,
Feb 9, 2016, 6:43:26 AM2/9/16
to AdWords API Forum
Hello Anthony,

Yes, when I changed library it is working fine with version v201509 and v201506, but not working with latest verison v201601.

Getting error "PHP Notice: Use of undefined constant ENT_XML1 - assumed 'ENT_XML1' in Google/Api/Ads/AdWords/Util/XmlSerializer.php on line 128
PHP Warning:  htmlspecialchars() expects parameter 2 to be long, string given in Google/Api/Ads/AdWords/Util/XmlSerializer.php on line 128

Thanks,

Nadine Sundquist (AdWords API Team)

unread,
Feb 9, 2016, 12:40:08 PM2/9/16
to AdWords API Forum
Hello,

It does look like a bug in our client library that was introduced in the last release. Just keep an eye on the bug you filed here. I saw that Vincent is already taking a look at it, and our team will update it as there is progress. Thanks for reporting this!

Regards,
Nadine, AdWords API Team
Reply all
Reply to author
Forward
0 new messages