Hi Tam, The bids element you mentioned is for ad groups, not campaigns which is that Tim was having problems with. Also, I ran some tests and there aren't any errors thrown when including the bids element in a SET operation. Do you have any SOAP XML logs showing this problem?
Best, - Eric On Dec 8, 6:20 am, Tam <tam.lani...@tradedoubler.com> wrote: > Hi Eric > > as mentioned above, we had a similar problem, which we resolved as > described above. I suspect this is a 'trap' that a lot of developers > who are working with your api are likely to fall into, so it might be > helpful to provide some messages in your error reporting which might > give some clues to help api developers to figure out where they're > going wrong on this issue! > > On Dec 2, 7:24 pm, AdWords API Advisor <adwordsapiadvi...@google.com> > wrote: > > > > > Hi Tim, > > > The error message will indicate which required fields are missing, and > > the documentation also has information on which fields are required, > > read-only, etc: > > > http://code.google.com/apis/adwords/v2009/docs/reference/CampaignServ... > > > Best, > > - Eric > > > On Dec 2, 1:45 pm, Timothy Merrifield <timothymerrifi...@gmail.com> > > wrote: > > > > Thanks Eric! > > > > Sounds great! But I just tried it out and got a required field error > > > on my mutate. How can a figure out what fields are required on a > > > Campaign object? > > > > On Nov 30, 1:21 pm, AdWords API Advisor <adwordsapiadvi...@google.com> > > > wrote: > > > > > Hi Tim, > > > > > When creating the new DTO you only need tosetthe required fields and > > > > the fields you want to change. Any fields not included in the request > > > > (setas null) will be left unchanged. For example, to pause an ad you > > > > only need the followingoperation: > > > > > <v20:operations> > > > > <v20:operator>SET</v20:operator> > > > > <v20:operand> > > > > <v20:adGroupId>XXXXX</v20:adGroupId> > > > > <v20:ad> > > > > <v20:id>XXXXX</v20:id> > > > > </v20:ad> > > > > <v20:status>PAUSED</v20:status> > > > > </v20:operand> > > > > </v20:operations> > > > > > Best, > > > > - Eric Koleda, AdWords API Team > > > > > On Nov 27, 3:19 pm, Timothy Merrifield <timothymerrifi...@gmail.com> > > > > wrote: > > > > > > Hey guys, > > > > > > I'm trying to mutate a campaign object but I'm running into a "Read- > > > > > only" error being throw. I found a previous thread that said that you > > > > > should create a new data transfer object and pass that into the mutate > > > > > function. Apparently this is because some fields are read-only and > > > > > passing in a DTO with those fieldssettriggers a read-only error. > > > > > > My problem is that I only want to mutate a single field, STATUS. I'm > > > > > afraid that if I create a new DTO that other fields could be mutated. > > > > > Even if I dosetall the fields to the pre-existing DTO, how can I be > > > > > sure that I get them all? This api call will modify our client's > > > > > campaigns so it's very important that I don't modify any other fields. > > > > > Is there any easy way to be certain that I only mutate a single field? > > > > > > Any advice would be great. Thanks! > > > > > Tim -- 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-...@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.
