Thank you for the reply, Josh, Yes, this does appear to be unique to the BatchJobService. I have not experienced this behavior elsewhere.
On Wednesday, May 3, 2017 at 5:50:18 PM UTC-4, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > Are you only seeing this issue with specific services, or only when using > BatchJobService > <https://developers.google.com/adwords/api/docs/reference/v201702/BatchJobService>? > > I ask because I just ran a few tests with AdGroupCriterionService > <https://developers.google.com/adwords/api/docs/reference/v201702/AdGroupCriterionService> > and AdGroupService > <https://developers.google.com/adwords/api/docs/reference/v201702/AdGroupService>, > > and the *fieldPathElements* were returned as expected (e.g., the first > element's index reflected the proper value). > > Thanks, > Josh, AdWords API Team > > On Wednesday, May 3, 2017 at 2:07:20 PM UTC-4, Phillip Pegelow wrote: >> >> >> The newest Perl library, v4.13.0 v201702, introduced the >> "fieldPathElements" field of ApiError. In testing prior to this upgrade, I >> have noticed that the first fieldPathElements.operations index is always 0 >> and the second fieldPathElements.operations index is the expected index of >> the failed job's error. >> >> Dumped ApiError.EntityNotFound xml object: >> <fieldPath>operations[20].operand.campaignId</fieldPath> >> <fieldPathElements> >> <field>operations</field> >> <index>0</index> >> </fieldPathElements> >> <fieldPathElements> >> <field>operations</field> >> <index>20</index> >> </fieldPathElements> >> <fieldPathElements> >> <field>operand</field> >> </fieldPathElements> >> <fieldPathElements> >> <field>campaignId</field> >> </fieldPathElements> >> <trigger>CampaignId: 111222333</trigger> >> <errorString>EntityNotFound.INVALID_ID</errorString> >> <ApiError.Type>EntityNotFound</ApiError.Type> >> <reason>INVALID_ID</reason> >> >> >> Is this behavior expected or is this a bug? If it is expected, should we >> always handle these errors by parsing the second "operations" attribute? >> >> We can also handle this appropriately by just parsing index from the >> fieldPath string, but according to the release notes ( >> https://developers.google.com/adwords/api/docs/reference/#getquery) we >> should be using the fieldPathElements instead. >> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/a982b66f-53bd-4871-87bc-0cc1baf704d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
