Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Ralph, No worries on the delayed response; I know what it's like to get caught up in code when you've made a breakthrough. It sounds like you'll be an expert on SOAP in no time. If you need any further help, you know where to find us! Have a wonderful day! Nadine, AdWords API Team On Friday

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Nadine-- Sorry for the delayed response--once this problem was solved i hit the ground running on my AdWords integration. Everything is working beautifully now, and I was far better able to debug other similar problems I ran into now that I have a better understanding of soap and the xml behi

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Ralph, Woohoo!!! I was holding my breath for a possible problem behind that one. I've probably spent a few too many cycles of my life staring at XML, and I've built SOAP XML from scratch before. I've had the same kind of gotcha moment. *What are namespaces?* Namespaces are created in XML to

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Holly Shit it worked! Thank you! Good catch by the way. How did you find that and how do i avoid this sort of thing in the future? What exactly are these namespaces and what's the cm/rm difference? Are these namespaces built in to soap protocol as just strings to separate services that go

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Oh Cool! I noticed the cm/rm dichotomy before but didn't remember to think about it for this problem. Thanks! I'll give that a try On Fri, Jan 8, 2016 at 7:50 AM, Nadine Sundquist (AdWords API Team) < adwordsapiadvisor+nad...@google.com> wrote: > Hi Ralph, > > Mike asked me to take a look at th

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Ralph, Mike asked me to take a look at this as well to see if I saw anything. I noticed something that *may* be causing the issue. I believe that you want to change: https://adwords.google.com/api/adwords/rm/v201509";> to https://adwords.google.com/api/adwords/cm/v201509

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Michael-- So I have continued to try this with the admin account on our production adwords account, and I'm always getting these same two errors: [OperatorError.OPERATOR_NOT_SUPPORTED @ operations[0], RequiredError.REQUIRED @ operations[0].operator]. To clarify, I did not get it to work on

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

That's sort of what I was thinking and that's why I used this other account. The accounts and permissions and stuff are pretty complex so i will go through again and make sure everything is in order there and report back. Thanks --Ralph On Wed, Jan 6, 2016 at 6:21 AM, Michael Cloonan (AdWords AP

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hello, The only thing I can think of if the request works on a test account but not on your production account is that possibly you actually don't have write permissions on your production account. Are you able to make mutate calls on any other services, or do you get this error on every mutate

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

HI Michael-- No problem! I was out of town too. Happy New Year! I fixed the unmarshalling issue, and on my test account, I finally got the error I was expecting: "AuthorizationError.USER_PERMISSION_DENIED" However when i switched over to make the call on our production account, It went back to

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hello, I apologize for the long delay in response. You should define your xmlns:ns0 on the soap:Envelope element, not on the RequestHeader. Note that the ns0:operator isn't within the RequestHeader, so that definition would be lost by the time you get to that part of the XML. Moving it up a lev

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Giving this a try. Still working on it but the first attempts have given me Unmarshalling errors i think due to "prefix unbound" right at the end of : http://schemas.xmlsoap.org/soap/envelope/";>soap:ClientUnmarshalling Error: ParseError at [row,col]:[1,761]\nMessage: http://www.w3.org/TR/1

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hello, I apologize; I actually made a mistake. The "choice"-type elements for rule items are actually one place where you do use a tag rather than XSI type. So, for example, the add_rule_based_remarketing_list.rb example from the Ruby client library generates a body that looks like this (signif

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Mike-- I got my client to build a request that looks just like yours, but now i'm getting the error about being unable to construct a ruleItem because it is abstract: Cannot construct an instance of com.google.ads.api.services.datax.userlists. rule.RuleItem because it is abstract. You are p

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Mike-- So I added the tag attributes you suggested. At first this gave me some new errors about my rule item key being malformed, etc. Once I fixed those, it went back to the same error: [OperatorError.OPERATOR_NOT_SUPPORTED @ operations[0], RequiredError.REQUIRED @ operations[0].operator]

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Awesome! Thanks for the in line edits!! That really helps to clear things up for me. I will work on this later today or tomorrow and get back to you with my success or next error message, ha ha. --Ralph On Wednesday, December 16, 2015 at 7:01:17 AM UTC-8, Michael Cloonan (AdWords API Team) w

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hello, Rather than have a tag , you should have . The fields for the ExpressionRuleUserList go directly within the operand. Similarly, instead of , you should have , and then the StringRuleItem attributes go directly within the tag. Just to make it cleaner, you should also remove the altoget

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Ok I have tried probably 30 combinations now. I still get the same error: `[OperatorError.OPERATOR_NOT_SUPPORTED @ operations[0], RequiredError.REQUIRED @ operations[0].operator]` Unless I mess up the whole operation in which case it adds to the errors list: `RequiredError.REQUIRED @ operatio

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Ralph, Thanks for providing the SOAP XML request. The RuleItem is associated with DateSpecificRuleUserList and ExpressionRuleUserList

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Oh btw, as I'm doing this in node, seeing this done in the java client library doesn't help much because it is so far abstracted meanwhile I am forced to build the request object manually. Is there some reason there is no node/js client library? --Ralph -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hi Umesh-- I have tried it like this too: but still get the same error: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:cm="https://adwords.google.com/api/adwords/cm/v201509"; xmlns:jaxb= "http://java.sun.com/xml/ns/jaxb"; xmlns:tns= "https://adwords.google.com/api/adwords/rm/v201509"; xmln

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

Hello, Thanks for providing the SOAP XML request and response logs. You are getting RequiredError.REQUIRED error as RuleItemGroup.items requires one of the RuleItem

ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

I am trying to create a new user list along with a rule for it. Should be pretty straight forward. But not working. Don't have a client library because doing this in node, (why is there no js sdk???) but my soap client works for some other requests. I made sure I wasn't using the manager ac