Hi Nadine, Thank you very much for investigating. Unfortunately, it *is* causing us an actual issue. That was the reason I originally posted. Because this particular feed is in this unusual state, we can't use the CampaignExtensionSettingService API to read and update our Callout Extensions. It's as if they do not exist via the API.
This is related to https://developers.google.com/adwords/api/docs/reference/v201710/CampaignExtensionSettingService. We are able to view and update other campaign extensions like Sitelinks and Structured Snippets, but we cannot view the Callouts. The document regarding migration (https://developers.google.com/adwords/api/docs/guides/extension-settings#migrate_ad_extensions_to_extension_setting_services) discusses migrating User feeds. It does not discuss migrating System Feeds. For this reason, I was reluctant to attempt to migrate it because I don't want to make anything worse. Best, Jon On Wednesday, January 24, 2018 at 1:18:13 PM UTC-8, Nadine Sundquist (AdWords API Team) wrote: > > Greetings Jon, > > Thanks for providing us with the additional information. It was really > helpful in double-checking a few things. I'm posting out on the forum > rather than directly replying just so both of us can help the general > community in case anyone else bumps into this. Feeds are always tricky. > When something is tagged with origin *ADWORDS* rather than *USER*, then > it is as you noticed, a system feed. When that's the case, you usually > can't make changes to it; there's a bit more about that here > <https://developers.google.com/adwords/api/docs/reference/v201710/FeedService.Feed.Origin>. > > I appreciate that you're being a good citizen and attempting to move things > over, but there are a few feeds that our system auto-generates, and the one > you discovered happened to be one of them. You can just leave it alone; no > migration is necessary. I would be surprised if it would even let you > mutate it. If you find that it's causing you issues, then please get back > to us, and we'll see what we can do to fix up that account for you. > > Cheers, > Nadine, AdWords API Team > > On Monday, January 22, 2018 at 10:28:10 PM UTC-5, Peter Oliquino wrote: >> >> Hi Jon, >> >> My apologies if I misunderstood. Moving forward, in order for me to >> better investigate and identify the cause why you are unable to retrieve >> the extensions, could you provide your clientCustomerId, the generated SOAP >> request and response when you attempted to retrieve the said extensions, >> and the AdWords UI screenshot containing them? You may reply to me >> privately via the *Reply privately to author* option. >> >> Thanks and regards, >> Peter >> 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 [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/b3a53415-f47c-48b6-ad5b-8ff0e3ebf6ea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
