Hi, You could exclude the problematic feed item ID(s) via a *FeedItemId NOT_IN [..., ..., ...]* predicate. That would allow you to retrieve all of the other feed items in your feeds. To fix the problematic feed items, you can update or remove them via the AdWords user interface or through a *FeedItemService.mutate* request.
Note that when I've seen data like this in the past, it's been due to users somehow adding the invalid values *outside* of the AdWords API (for example, through AdWords Editor, Bulk uploads, or the AdWords user interface). I don't foresee us adding special encoding rules to the AdWords API for these cases, since that would mean all clients would have to understand how to interpret those rules. Thanks, Josh, AdWords API Team On Friday, December 8, 2017 at 3:37:19 PM UTC-5, Caihua Du wrote: > > Thank you Josh for looking into it. Is that possible we skip sending the > invalid character to the response or we convert to some encoded format? We > had similar issue last year from AdWords and I believe the solved it early > this year. Not sure if we can use the same pattern here. > > On Thursday, December 7, 2017 at 11:29:26 AM UTC-8, Josh Radcliff (AdWords > API Team) wrote: >> >> Hi, >> >> The reason that error is being thrown is that the underlying data in (at >> least) one particular feed item is invalid. Specifically, the string value >> for attribute ID 3 in feed ID 23642780/feed item ID 957498860 contains >> unicode character 031. If you update that feed item through the UI or the >> AdWords API so it contains valid characters, you should be all set. >> >> Thanks, >> Josh, AdWords API Team >> >> On Thursday, December 7, 2017 at 12:52:29 PM UTC-5, Caihua Du wrote: >>> >>> Hi Vincent, >>> >>> I haven sent you the SOAP requestID privately, can you please take a >>> look? We have two new instance of this failure again today. Thank you very >>> much! >>> >>> On Wednesday, December 6, 2017 at 12:52:07 AM UTC-8, Vincent Racaza >>> (AdWords API Team) wrote: >>>> >>>> Hi Caihua, >>>> >>>> Could you provide the SOAP request and response logs instead with the >>>> clientCustomerId so I can investigate further? To get all the success and >>>> failed SOAP request and response, you can change all the INFO >>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/log4j.properties#L31> >>>> level >>>> to DEBUG in the log4j.properties >>>> <https://github.com/googleads/googleads-java-lib/blob/master/examples/adwords_axis/src/main/resources/log4j.properties> >>>> file >>>> (in Java). If you are using other client libraries, you can also do the >>>> same in their log property file. Please use the *Reply privately to >>>> author* option when replying. >>>> >>>> Thanks, >>>> Vincent >>>> AdWords API Team >>>> >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/713430ee-4b1a-4b58-bd41-cc448733e69f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
