Actually that is not strictly true Kevin. I re-created a report via the API yesterday and it did exactly the same thing?
On Aug 11, 4:14 pm, Kevin Winter <kevin.win...@google.com> wrote: > Hi All, > I just wanted to let everyone know we are aware of the problem. This only > seems to affect reports that were created in the UI and are being downloaded > via the API. We're still researching the best solution given that some of > the fields in the reports are not allowed in API reports. In the meantime, > redefining the report via the API and using that moving forward permanently > fixes the issue for an individual report (since it will not longer have the > fields that only the UI can add). > > We'll be sure to let you know when we have a fix. > > - Kevin Winter > AdWords API Team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
