Oh, and to add to this... I'm not sure why they changed the
CustomerReportJob model to begin with. It worked flawlessly. Requiring
a DefinedReportJob to have the AdID and DestinationURL columns makes
no sense and requires us to completely rethink our current working
solution. At this moment, I'm not sure I see an easy work around.
Hey Google, can't the Custom Report Job stay the way it is????? *hint
hint*
It took me a while to come up with a good working solution for our
needs and I'm really not looking forward to it breaking.
I can only hope its that simple. I'm sure they realize that there is a
lot of code that will break and processes that will not be able to
work correctly without those IDs.
Right Google??? *hint hint*
On Oct 19, 4:05 am, "zdvs...@hotmail.com"
<zdvs...@hotmail.com> wrote:
Ad/Creative ids are missing too.
I assume they're only missing in the documentation, if anyone finds
out...- Hide quoted text -
- Show quoted text -