Hi Phil,

We're actively working on a fix for this. I'll update this post as soon as 
it's in place.

Thanks,
Josh, AdWords API Team

On Monday, May 8, 2017 at 10:14:52 AM UTC-4, Phillip Pegelow wrote:
>
> Any update on this?
>
> Thanks,
> Phil
>
> On Thursday, May 4, 2017 at 3:53:58 PM UTC-4, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi,
>>
>> Thanks for confirming. I tried this out as well and confirmed that there 
>> is an extra *fieldPathElement* in errors from *BatchJobService*, but not 
>> in errors from the synchronous services. I've asked the batch job team to 
>> investigate and will post back here as soon as I have an update from them.
>>
>> Thanks,
>> Josh, AdWords API Team
>>
>> On Thursday, May 4, 2017 at 10:05:00 AM UTC-4, Phillip Pegelow wrote:
>>>
>>> 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 adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 adwords-api+unsubscr...@googlegroups.com.
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/3779ec30-a77c-4640-8d41-bfc14ec6a416%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • Unexpected ApiErr... Phillip Pegelow
    • Re: Unexpect... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
      • Re: Unex... Phillip Pegelow
        • Re: ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
          • ... Phillip Pegelow
            • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
              • ... Christian
                • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
                • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
                • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
                • ... Christian
                • ... Phillip Pegelow
                • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
                • ... Christian
                • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum

Reply via email to