I'm trying to migrate our code to use the v2009 API, and I must say, that I'm finding OGNL expressions too bulky for error reporting. I also can't imagine a use case, that you had in mind for the OGNL expression. Most of the time we want to know only the index of the item, that caused the fault, so that we can retry the remaining items. The extra information is useful, but most of the time will have to be manually reviewed anyway (e.g. whether an exemption request should be filed, or whether the keyword is junk).
I haven't been able to find any examples of error handling in your Java code samples for v2009. I have been using the regexp "operations\ [(\d+)\]" to find the index of the failed item. Is this a good way to do so, or is there a better way to achieve this? Alex On Sep 24, 9:08 am, AdWords API Advisor <adwordsapiadvi...@google.com> wrote: > Hi, > > In thev2009API the OGNL expression was provided for that very > purpose. You may also be able to glean some information about the > offending object by looking at the trigger field of theerror. > > Best, > - Eric Koleda, AdWords API Team > > On Sep 24, 10:12 am, "stel...@smecsells.com" <stel...@smecsells.com> > wrote: > > > Say I'm adding multiple ads to an ad group, and a policy violation > >erroroccurs. Is there a simple possibility to determine which ad the > >errorrelates to, other than inspecting the OGNL expression? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
