Re: FeedItem service returns invalid characters.

Hi, Yes, I think that's the best approach. If they export their feed items to a CSV, it should be pretty easy to see the unprintable characters, and then they can fix those through the user interface. Thanks, Josh, AdWords API Team On Friday, December 8, 2017 at 7:06:36 PM UTC-5, Caihua Du

Re: FeedItem service returns invalid characters.

Got it. In our case, customer is using our tool to get FeedItem data, and we are not able to modify the invalid data for them without their permission and hence mutate operation may not be an option for us. It seems to me there is no other way to fix unless customer update their data

Re: FeedItem service returns invalid characters.

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

Re: FeedItem service returns invalid characters.

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,

Re: FeedItem service returns invalid characters.

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

Re: FeedItem service returns invalid characters.

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

Re: FeedItem service returns invalid characters.

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

Re: FeedItem service returns invalid characters.

Hi there, This issues shows up again, we have at least two customers that have encountered this issue. Here is the latest call stack of this exception. Please let me know if you need the request id for further investigation: System.Xml.XmlException: Data at the root level is invalid. Line 1,

Re: FeedItem service returns invalid characters.

Sorry for the late response Vincent. I haven't seen this issue shows up again lately. I will let you know if see the same issue again. Thanks, Caihua. On Sunday, October 15, 2017 at 9:23:35 PM UTC-7, Vincent Racaza (AdWords API Team) wrote: > > Hi Caihua, > > Could you confirm if this latest

Re: FeedItem service returns invalid characters.

Hi Caihua, A gentle follow up on this. If you still have issues regarding this, then kindly provide the details that I asked on my previous reply. Thanks, Vincent AdWords API Team -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+:

Re: FeedItem service returns invalid characters.

Hi Caihua, Could you confirm if this latest issue is targeting the clientCustomerId same as your old forum thread ? If so, then

Re: FeedItem service returns invalid characters.

BTW, this is the old issue we reported before: https://groups.google.com/forum/#!searchin/adwords-api/Unknown$20exception$20when$20calling$20FeedItemService%7Csort:relevance/adwords-api/21w2Uck4LR8/RiUf2pEICQAJ On Sunday, October 15, 2017 at 10:25:22 AM UTC-7, Caihua Du wrote: > > Hi there, >

FeedItem service returns invalid characters.

Hi there, We found that when we call FeedItemService, the response contains invalid charters in the xml body. We saw similar issue at the early of this year and AdWords fixed this, it seems we have seen this issue again. Can you please look into this? Response is not well-formed XML. --->