I have been having the same problem over on another thread, and without wishing to suggest that this won't work for some, I do know that I created reports yesterday directly from the API and still have the same sort of problem: This seems to be the favourite
ReportDefinitionError.INVALID_REPORT_DEFINITION_ID@selector.selector although this one copmes up as well ReportDefinitionError.INVALID_FIELD_NAME_FOR_REPORT@PrimaryDisplayStatus Anyway, in a normal forum some moderator would merge the threads, but.... :-) On Aug 10, 10:22 pm, Jon Brown <jcb...@gmail.com> wrote: > Understood. There was some combination of things that wouldn't allow > me to do it that way at the time. I think it had to do with old versus > new reports for MCC account cross-client reports. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
