Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Nadine Sundquist (AdWords API Team)]

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, January 22, 2016 at 7:29:00 PM UTC-5, ra...@woopra.com wrote:
>
> 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 
> behind it.
>
> Thank you so much for your detailed explanation!  This soap stuff makes 
> much better sense now! ha ha.  As does the wsdl.  I was using a soap client 
> to compile the xml...not sure why it missed these lines: 
>
> http://www.w3.org/2001/XMLSchema; xmlns:cm="
> https://adwords.google.com/api/adwords/cm/v201509;... 
> 
>
> But now i can check!
>
> I really appreciate you taking the time to teach me this.  Above and 
> beyond...
>
> Thanks again,
> --Ralph
>
> On Monday, January 11, 2016 at 1:12:55 PM UTC-8, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> 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 avoid naming conflicts. The closest 
>> concept I can reference is a Java package. You can have two classes with 
>> the same name in two different Java packages. The way it relates to the 
>> AdWords API is that some of our services live in separate namespaces. 
>> Sometimes, one service may reference components that come from another 
>> namespace. That's what happened to you here.
>>
>> *How do I avoid this in the future?*
>>
>> *Option 1*
>> The way we avoid this in the client libraries is that we use tools (such 
>> as Apache Axis or Apache CXF for Java) to generate code from the existing 
>> WSDLs (definitions of each AdWords API service). I haven't given it a try 
>> myself, but there's probably something for js as well.
>>
>> *Option 2*
>> ** Short Explanation*
>> If you're checking this manually, you can use a tool to check your XML 
>> against the WSDL that we provide. Just Google *validate XML against WSDL*. 
>> There are a couple of options that will come up for free tools. If you're 
>> thinking, "What's a WSDL, and where do I find it for the AdWords API?", 
>> read on.
>> ** Long Explanation*
>> If you're not using that many services, then you may not want to go 
>> through the effort of doing this. However, you want to double-check that 
>> you have the right namespaces by manually checking. WSDLs to the rescue! 
>> So, let's say you want to check out the AdWordsUserListService 
>> .
>>  
>> You would go to that page in the documentation for that service 
>> ,
>>  
>> and you would click on the link under Production WSDL 
>> .
>>  
>> Every service has one of these. You'll notice in the URL, that you'll see 
>> the namespace for that service e.g. 
>> https://adwords.google.com/api/adwords/rm/v201509/AdwordsUserListService?wsdl
>>  
>> has the *rm*. The *targetNamespace* is also defined the same way. For 
>> your *OPERATOR* example, Look for *OPERATOR* in the file. Then work your 
>> way up the XML structure until you find a namespace. You'll then bump into 
>> the namespace with the *cm* in it. Rather than eyeballing it, it's nice 
>> to have a tool double-check your XML for you.
>>
>> Happy coding,
>> Nadine, AdWords API Team
>>
>> On Friday, January 8, 2016 at 6:50:47 PM UTC-5, ra...@woopra.com wrote:
>>>
>>> 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 over the same http interface? (the url doesn't seem to 
>>> lead anywhere) Or are the urls actually providing some resource to the soap 
>>> server to configure it for the request?
>>>
>>> I am very new to soap.
>>>
>>> Thanks for all the help guys!
>>> --Ralph
>>>
>>> On Friday, January 8, 2016 at 7:50:55 AM UTC-8, Nadine Sundquist 
>>> (AdWords API Team) wrote:

 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:

 

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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 
behind it.

Thank you so much for your detailed explanation!  This soap stuff makes 
much better sense now! ha ha.  As does the wsdl.  I was using a soap client 
to compile the xml...not sure why it missed these lines: 

http://www.w3.org/2001/XMLSchema; xmlns:cm="
https://adwords.google.com/api/adwords/cm/v201509;... 


But now i can check!

I really appreciate you taking the time to teach me this.  Above and 
beyond...

Thanks again,
--Ralph

On Monday, January 11, 2016 at 1:12:55 PM UTC-8, Nadine Sundquist (AdWords 
API Team) wrote:
>
> 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 avoid naming conflicts. The closest 
> concept I can reference is a Java package. You can have two classes with 
> the same name in two different Java packages. The way it relates to the 
> AdWords API is that some of our services live in separate namespaces. 
> Sometimes, one service may reference components that come from another 
> namespace. That's what happened to you here.
>
> *How do I avoid this in the future?*
>
> *Option 1*
> The way we avoid this in the client libraries is that we use tools (such 
> as Apache Axis or Apache CXF for Java) to generate code from the existing 
> WSDLs (definitions of each AdWords API service). I haven't given it a try 
> myself, but there's probably something for js as well.
>
> *Option 2*
> ** Short Explanation*
> If you're checking this manually, you can use a tool to check your XML 
> against the WSDL that we provide. Just Google *validate XML against WSDL*. 
> There are a couple of options that will come up for free tools. If you're 
> thinking, "What's a WSDL, and where do I find it for the AdWords API?", 
> read on.
> ** Long Explanation*
> If you're not using that many services, then you may not want to go 
> through the effort of doing this. However, you want to double-check that 
> you have the right namespaces by manually checking. WSDLs to the rescue! 
> So, let's say you want to check out the AdWordsUserListService 
> .
>  
> You would go to that page in the documentation for that service 
> ,
>  
> and you would click on the link under Production WSDL 
> .
>  
> Every service has one of these. You'll notice in the URL, that you'll see 
> the namespace for that service e.g. 
> https://adwords.google.com/api/adwords/rm/v201509/AdwordsUserListService?wsdl 
> has the *rm*. The *targetNamespace* is also defined the same way. For 
> your *OPERATOR* example, Look for *OPERATOR* in the file. Then work your 
> way up the XML structure until you find a namespace. You'll then bump into 
> the namespace with the *cm* in it. Rather than eyeballing it, it's nice 
> to have a tool double-check your XML for you.
>
> Happy coding,
> Nadine, AdWords API Team
>
> On Friday, January 8, 2016 at 6:50:47 PM UTC-5, ra...@woopra.com 
>  wrote:
>>
>> 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 over the same http interface? (the url doesn't seem to 
>> lead anywhere) Or are the urls actually providing some resource to the soap 
>> server to configure it for the request?
>>
>> I am very new to soap.
>>
>> Thanks for all the help guys!
>> --Ralph
>>
>> On Friday, January 8, 2016 at 7:50:55 AM UTC-8, Nadine Sundquist (AdWords 
>> API Team) wrote:
>>>
>>> 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 
>>> ">
>>>
>>> I'm hoping it's as simple as changing one character.
>>>
>>> You mentioned wanting to see what one of the client libraries will 
>>> output. Here's what Perl outputs; this is only the first part because it's 
>>> a bit wordy. You can see why I'm thinking a one letter change may make a 
>>> difference.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Nadine Sundquist (AdWords API Team)]

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 avoid naming conflicts. The closest 
concept I can reference is a Java package. You can have two classes with 
the same name in two different Java packages. The way it relates to the 
AdWords API is that some of our services live in separate namespaces. 
Sometimes, one service may reference components that come from another 
namespace. That's what happened to you here.

*How do I avoid this in the future?*

*Option 1*
The way we avoid this in the client libraries is that we use tools (such as 
Apache Axis or Apache CXF for Java) to generate code from the existing 
WSDLs (definitions of each AdWords API service). I haven't given it a try 
myself, but there's probably something for js as well.

*Option 2*
** Short Explanation*
If you're checking this manually, you can use a tool to check your XML 
against the WSDL that we provide. Just Google *validate XML against WSDL*. 
There are a couple of options that will come up for free tools. If you're 
thinking, "What's a WSDL, and where do I find it for the AdWords API?", 
read on.
** Long Explanation*
If you're not using that many services, then you may not want to go through 
the effort of doing this. However, you want to double-check that you have 
the right namespaces by manually checking. WSDLs to the rescue! So, let's 
say you want to check out the AdWordsUserListService 
.
 
You would go to that page in the documentation for that service 
,
 
and you would click on the link under Production WSDL 
.
 
Every service has one of these. You'll notice in the URL, that you'll see 
the namespace for that service e.g. 
https://adwords.google.com/api/adwords/rm/v201509/AdwordsUserListService?wsdl 
has the *rm*. The *targetNamespace* is also defined the same way. For your 
*OPERATOR* example, Look for *OPERATOR* in the file. Then work your way up 
the XML structure until you find a namespace. You'll then bump into the 
namespace with the *cm* in it. Rather than eyeballing it, it's nice to have 
a tool double-check your XML for you.

Happy coding,
Nadine, AdWords API Team

On Friday, January 8, 2016 at 6:50:47 PM UTC-5, ra...@woopra.com wrote:
>
> 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 over the same http interface? (the url doesn't seem to 
> lead anywhere) Or are the urls actually providing some resource to the soap 
> server to configure it for the request?
>
> I am very new to soap.
>
> Thanks for all the help guys!
> --Ralph
>
> On Friday, January 8, 2016 at 7:50:55 AM UTC-8, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> 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 
>> ">
>>
>> I'm hoping it's as simple as changing one character.
>>
>> You mentioned wanting to see what one of the client libraries will 
>> output. Here's what Perl outputs; this is only the first part because it's 
>> a bit wordy. You can see why I'm thinking a one letter change may make a 
>> difference.
>>
>>  https://adwords.google.com/api/adwords/rm/v201509;> 
>>  > xmlns="https://adwords.google.com/api/adwords/cm/v201509;>ADD 
>>  Expression based user list 
>> created at 20160108_103956 Users who checked out in six 
>> month window OR visited the checkout page with more than one item in their 
>> cart 
>>
>> Cheers,
>>
>> Nadine, AdWords API Team
>>
>> On Thursday, January 7, 2016 at 4:28:39 PM UTC-5, ra...@woopra.com wrote:
>>>
>>> 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 the test account, I mis-spoke when I said it worked 
>>> there.  I get these errors when using a test manager account, a production 
>>> manager account, and a production client account.  I get the user 
>>> permission 

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Ralph Samuel]

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 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
> ">
>
> I'm hoping it's as simple as changing one character.
>
> You mentioned wanting to see what one of the client libraries will output.
> Here's what Perl outputs; this is only the first part because it's a bit
> wordy. You can see why I'm thinking a one letter change may make a
> difference.
>
>  https://adwords.google.com/api/adwords/rm/v201509;> 
>   xmlns="https://adwords.google.com/api/adwords/cm/v201509;>ADD 
>  Expression based user list 
> created at 20160108_103956 Users who checked out in six 
> month window OR visited the checkout page with more than one item in their 
> cart 
>
> Cheers,
>
> Nadine, AdWords API Team
>
> On Thursday, January 7, 2016 at 4:28:39 PM UTC-5, ra...@woopra.com wrote:
>>
>> 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 the test account, I mis-spoke when I said it worked
>> there.  I get these errors when using a test manager account, a production
>> manager account, and a production client account.  I get the user
>> permission denied on a different unused production client account for some
>> reason (possibly because there is no credit card on file for it yet?)  I do
>> not actually have a test client account under my test manager account.
>>
>> I think all this about my accounts is accurate, but all the different
>> kinds of accounts and their functionality is pretty complex so I can't be
>> sure ha ha.
>>
>> I don't think it is a permissions issue as I only have admins on the
>> accounts, and my xml requests look almost exactly like the examples I've
>> found in the docs and from you in this thread.  I am sort of at a loss as
>> to what is going on.  I am considering using one of your client libraries
>> to manually make the call and compare the raw xml to mine as a next step.
>>
>> If you have any other ideas for what I could try, I'm open to suggestions.
>>
>> --Ralph
>>
> --
> --
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
> Also find us on our blog and Google+:
> https://googleadsdeveloper.blogspot.com/
> https://plus.google.com/+GoogleAdsDevelopers/posts
> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>
> 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
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "AdWords API Forum" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/adwords-api/osBZcV05iqo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> adwords-api+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/adwords-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/adwords-api/ed1bf410-d16e-428a-b80d-473824337840%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the 

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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 over the same http interface? (the url doesn't seem to 
lead anywhere) Or are the urls actually providing some resource to the soap 
server to configure it for the request?

I am very new to soap.

Thanks for all the help guys!
--Ralph

On Friday, January 8, 2016 at 7:50:55 AM UTC-8, Nadine Sundquist (AdWords 
API Team) wrote:
>
> 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 
> ">
>
> I'm hoping it's as simple as changing one character.
>
> You mentioned wanting to see what one of the client libraries will output. 
> Here's what Perl outputs; this is only the first part because it's a bit 
> wordy. You can see why I'm thinking a one letter change may make a 
> difference.
>
>  https://adwords.google.com/api/adwords/rm/v201509;> 
>   xmlns="https://adwords.google.com/api/adwords/cm/v201509;>ADD 
>  Expression based user list 
> created at 20160108_103956 Users who checked out in six 
> month window OR visited the checkout page with more than one item in their 
> cart 
>
> Cheers,
>
> Nadine, AdWords API Team
>
> On Thursday, January 7, 2016 at 4:28:39 PM UTC-5, ra...@woopra.com 
>  wrote:
>>
>> 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 the test account, I mis-spoke when I said it worked 
>> there.  I get these errors when using a test manager account, a production 
>> manager account, and a production client account.  I get the user 
>> permission denied on a different unused production client account for some 
>> reason (possibly because there is no credit card on file for it yet?)  I do 
>> not actually have a test client account under my test manager account.  
>>
>> I think all this about my accounts is accurate, but all the different 
>> kinds of accounts and their functionality is pretty complex so I can't be 
>> sure ha ha.
>>
>> I don't think it is a permissions issue as I only have admins on the 
>> accounts, and my xml requests look almost exactly like the examples I've 
>> found in the docs and from you in this thread.  I am sort of at a loss as 
>> to what is going on.  I am considering using one of your client libraries 
>> to manually make the call and compare the raw xml to mine as a next step.
>>
>> If you have any other ideas for what I could try, I'm open to suggestions.
>>
>> --Ralph
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/4ba95a3b-bdbf-48ea-bde8-0137a11dec18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Nadine Sundquist (AdWords API Team)]

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 
">

I'm hoping it's as simple as changing one character.

You mentioned wanting to see what one of the client libraries will output. 
Here's what Perl outputs; this is only the first part because it's a bit 
wordy. You can see why I'm thinking a one letter change may make a 
difference.

 https://adwords.google.com/api/adwords/rm/v201509;> 
 https://adwords.google.com/api/adwords/cm/v201509;>ADD 
 Expression based user list 
created at 20160108_103956 Users who checked out in six 
month window OR visited the checkout page with more than one item in their 
cart 

Cheers,

Nadine, AdWords API Team

On Thursday, January 7, 2016 at 4:28:39 PM UTC-5, ra...@woopra.com wrote:
>
> 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 the test account, I mis-spoke when I said it worked 
> there.  I get these errors when using a test manager account, a production 
> manager account, and a production client account.  I get the user 
> permission denied on a different unused production client account for some 
> reason (possibly because there is no credit card on file for it yet?)  I do 
> not actually have a test client account under my test manager account.  
>
> I think all this about my accounts is accurate, but all the different 
> kinds of accounts and their functionality is pretty complex so I can't be 
> sure ha ha.
>
> I don't think it is a permissions issue as I only have admins on the 
> accounts, and my xml requests look almost exactly like the examples I've 
> found in the docs and from you in this thread.  I am sort of at a loss as 
> to what is going on.  I am considering using one of your client libraries 
> to manually make the call and compare the raw xml to mine as a next step.
>
> If you have any other ideas for what I could try, I'm open to suggestions.
>
> --Ralph
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/ed1bf410-d16e-428a-b80d-473824337840%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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 the test account, I mis-spoke when I said it worked 
there.  I get these errors when using a test manager account, a production 
manager account, and a production client account.  I get the user 
permission denied on a different unused production client account for some 
reason (possibly because there is no credit card on file for it yet?)  I do 
not actually have a test client account under my test manager account.  

I think all this about my accounts is accurate, but all the different kinds 
of accounts and their functionality is pretty complex so I can't be sure ha 
ha.

I don't think it is a permissions issue as I only have admins on the 
accounts, and my xml requests look almost exactly like the examples I've 
found in the docs and from you in this thread.  I am sort of at a loss as 
to what is going on.  I am considering using one of your client libraries 
to manually make the call and compare the raw xml to mine as a next step.

If you have any other ideas for what I could try, I'm open to suggestions.

--Ralph

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/be91a4c7-9fb7-49e0-b499-f7cbcdb480bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Ralph Samuel]

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 API Team) <
adwordsapiadvisor+mich...@google.com> wrote:

> 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 call
> for this account? You may have to regenerate your refresh token from an
> account that has full admin permissions.
>
> Regards,
> Mike, AdWords API Team
>
>
> On Tuesday, January 5, 2016 at 6:41:14 PM UTC-5, ra...@woopra.com wrote:
>
>> 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 the same error: "[OperatorError.OPERATOR_NOT_SUPPORTED @
>> operations[0], RequiredError.REQUIRED @ operations[0].operator]"
>>
>>
>> My soap client does not seem to allow me to add custom attributes to the
>> envelope but I added the ns0 on the operations tag.  (Also adding
>> validateOnly as testing on production account now.
>> Here was my request:
>>
>> > xmlns:soap="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; 
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
>>
>>   > xmlns:ns1="https://adwords.google.com/api/adwords/rm/v201509; 
>> xmlns="https://adwords.google.com/api/adwords/rm/v201509;>
>>  Woopra:AppConnect:getTrackers
>>  XXX
>>  XXX
>>  true
>>   
>>
>>
>>   https://adwords.google.com/api/adwords/rm/v201509;>
>>  > xmlns:ns0="https://adwords.google.com/api/adwords/rm/v201509;>
>> ADD
>> 
>>Woopra_test_label_Id
>>This User List has been created to mirror the 
>> woopra label.
>>test_label_Id
>>
>>   
>>  
>> 
>>
>>   Woopra_test_label_Id
>>
>>EQUALS
>>true
>> 
>>  
>>   
>>
>> 
>>  
>>   
>>
>>
>>
>>
>> Sorry for all this.  I really do wish there was a node library...
>> --Ralph
>>
>> On Monday, January 4, 2016 at 6:52:39 AM UTC-8, Michael Cloonan (AdWords
>> API Team) wrote:
>>
>> 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 level
>> will ensure the definition is still found.
>>
>> Regards,
>> Mike, AdWords API Team
>>
>> On Friday, December 18, 2015 at 7:38:24 PM UTC-5, ra...@woopra.com wrote:
>>
>> 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
>> :
>>
>> > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/;>soap:ClientUnmarshalling
>> Error: ParseError at [row,col]:[1,761]\nMessage:
>> http://www.w3.org/TR/1999/REC-xml-names-19990114#ElementPrefixUnbound?ns0ns0:operator
>> 
>>
>> This is my first time interacting with soap api so Im not sure if this
>> could be related to my envelope being off or what.  Trying more things now.
>>
>>
>> Oh here's the whole request btw in case you can spot something faster:
>>
>> Ok something is wrong because my xml formatter throws the same error so
>> here it is raw:
>>
>> http://schemas.xmlsoap.org/soap/envelope/;
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;  xmlns:tns="
>> https://adwords.google.com/api/adwords/rm/v201509; xmlns:jaxb="
>> http://java.sun.com/xml/ns/jaxb; xmlns:cm="
>> https://adwords.google.com/api/adwords/cm/v201509;
>> >https://adwords.google.com/api/adwords/rm/v201509; xmlns="
>> https://adwords.google.com/api/adwords/rm/v201509;>
>> Woopra:AppConnect:getTrackersX
>> 4579826953
>> > xmlns="https://adwords.google.com/api/adwords/rm/v201509;
>> >ADD> "ExpressionRuleUserList">Woopra_test_label_IdThis
>> User List has been created to mirror the woopra label.
>> test_label_Id
>> 
>> Woopra_test_label_IdEQUALStrue
>> 
>>
>>
>>
>>

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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 the same error: "[OperatorError.OPERATOR_NOT_SUPPORTED @ 
operations[0], RequiredError.REQUIRED @ operations[0].operator]"


My soap client does not seem to allow me to add custom attributes to the 
envelope but I added the ns0 on the operations tag.  (Also adding 
validateOnly as testing on production account now.
Here was my request:

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; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
   
  https://adwords.google.com/api/adwords/rm/v201509; 
xmlns="https://adwords.google.com/api/adwords/rm/v201509;>
 Woopra:AppConnect:getTrackers
 XXX
 XXX
 true
  
   
   
  https://adwords.google.com/api/adwords/rm/v201509;>
 https://adwords.google.com/api/adwords/rm/v201509;>
ADD

   Woopra_test_label_Id
   This User List has been created to mirror the 
woopra label.
   test_label_Id
   
  
 

   
  Woopra_test_label_Id
   
   EQUALS
   true

 
  
   

 
  
   



Sorry for all this.  I really do wish there was a node library...
--Ralph

On Monday, January 4, 2016 at 6:52:39 AM UTC-8, Michael Cloonan (AdWords 
API Team) wrote:
>
> 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 level 
> will ensure the definition is still found.
>
> Regards,
> Mike, AdWords API Team
>
> On Friday, December 18, 2015 at 7:38:24 PM UTC-5, ra...@woopra.com 
>  wrote:
>>
>> 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 
>> :
>>  
>> > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/;>soap:ClientUnmarshalling
>>  
>> Error: ParseError at [row,col]:[1,761]\nMessage: 
>> http://www.w3.org/TR/1999/REC-xml-names-19990114#ElementPrefixUnbound?ns0ns0:operator
>>  
>> 
>>
>> This is my first time interacting with soap api so Im not sure if this 
>> could be related to my envelope being off or what.  Trying more things now. 
>>  
>>
>> Oh here's the whole request btw in case you can spot something faster: 
>>
>> Ok something is wrong because my xml formatter throws the same error so 
>> here it is raw:
>>
>> http://schemas.xmlsoap.org/soap/envelope/; 
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;  xmlns:tns="
>> https://adwords.google.com/api/adwords/rm/v201509; xmlns:jaxb="
>> http://java.sun.com/xml/ns/jaxb; xmlns:cm="
>> https://adwords.google.com/api/adwords/cm/v201509;
>> >https://adwords.google.com/api/adwords/rm/v201509; xmlns="
>> https://adwords.google.com/api/adwords/rm/v201509;>
>> Woopra:AppConnect:getTrackersX
>> 4579826953
>> > xmlns="https://adwords.google.com/api/adwords/rm/v201509;
>> >ADD> "ExpressionRuleUserList">Woopra_test_label_IdThis 
>> User List has been created to mirror the woopra label.
>> test_label_Id
>> 
>> Woopra_test_label_IdEQUALStrue
>> 
>>
>>
>>
>>
>>
>> On Thursday, December 17, 2015 at 3:01:08 PM UTC-8, ra...@woopra.com 
>> wrote:
>>>
>>> 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 probably 
>>> missing an @Uses annotation while invoking public abstract com.google.
>>> ads.api.services.datax.userlists.UserListReturnValue com.google.ads.api.
>>> services.datax.adwordsuserlist.AdwordsUserListService.mutate(java.util.
>>> List) throws com.google.ads.api.services.common.error.ApiException with 
>>> params [[com.google.ads.api.services.datax.adwordsuserlist.v201509.
>>> jaxbgen.UserListOperation@47c87410]].
>>>
>>> I've seen your answers to a couple other posts about similar statements, 
>>> but the format of the xml requests in the answers in those threads are 
>>> different enough that I can't adapt them to my own.  Here is the body of my 
>>> request fixed 

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Michael Cloonan (AdWords API Team)]

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 level 
will ensure the definition is still found.

Regards,
Mike, AdWords API Team

On Friday, December 18, 2015 at 7:38:24 PM UTC-5, ra...@woopra.com wrote:
>
> 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 
> :
>  
>  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/;>soap:ClientUnmarshalling
>  
> Error: ParseError at [row,col]:[1,761]\nMessage: 
> http://www.w3.org/TR/1999/REC-xml-names-19990114#ElementPrefixUnbound?ns0ns0:operator
>  
> 
>
> This is my first time interacting with soap api so Im not sure if this 
> could be related to my envelope being off or what.  Trying more things now. 
>  
>
> Oh here's the whole request btw in case you can spot something faster: 
>
> Ok something is wrong because my xml formatter throws the same error so 
> here it is raw:
>
> http://schemas.xmlsoap.org/soap/envelope/; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;  xmlns:tns="
> https://adwords.google.com/api/adwords/rm/v201509; xmlns:jaxb="
> http://java.sun.com/xml/ns/jaxb; xmlns:cm="
> https://adwords.google.com/api/adwords/cm/v201509;
> >https://adwords.google.com/api/adwords/rm/v201509; xmlns="
> https://adwords.google.com/api/adwords/rm/v201509;>
> Woopra:AppConnect:getTrackersX
> 4579826953
>  xmlns="https://adwords.google.com/api/adwords/rm/v201509;
> >ADD "ExpressionRuleUserList">Woopra_test_label_IdThis 
> User List has been created to mirror the woopra label.
> test_label_Id
> 
> Woopra_test_label_IdEQUALStrue
> 
>
>
>
>
>
> On Thursday, December 17, 2015 at 3:01:08 PM UTC-8, ra...@woopra.com 
> wrote:
>>
>> 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 probably 
>> missing an @Uses annotation while invoking public abstract com.google.ads
>> .api.services.datax.userlists.UserListReturnValue com.google.ads.api.
>> services.datax.adwordsuserlist.AdwordsUserListService.mutate(java.util.
>> List) throws com.google.ads.api.services.common.error.ApiException with 
>> params [[com.google.ads.api.services.datax.adwordsuserlist.v201509.
>> jaxbgen.UserListOperation@47c87410]].
>>
>> I've seen your answers to a couple other posts about similar statements, 
>> but the format of the xml requests in the answers in those threads are 
>> different enough that I can't adapt them to my own.  Here is the body of my 
>> request fixed to look like yours:
>>
>>
>>   
>>   https://adwords.google.com/api/adwords/rm/v201509;>
>>  
>> ADD
>> 
>>Woopra_test_label_Id
>>test_label_Id
>>
>>   
>>  
>> 
>>Woopra_test_label_Id
>> 
>> EQUALS
>> true
>>  
>>   
>>
>> 
>>  
>>   
>>
>>
>>
>>
>> thanks
>> --Ralph
>>
>>
>> On Wednesday, December 16, 2015 at 7:01:17 AM UTC-8, Michael Cloonan 
>> (AdWords API Team) wrote:
>>>
>>> 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  altogether, rather than 
>>> specifying it as nil.
>>>
>>> I am confused about why you're getting an error pointing to the 
>>> operator, but hopefully cleaning up the operand to have the correct format 
>>> by following the instructions above will fix it anyway.
>>>
>>> Just to be clear, the SOAP body you posted most recently, with 
>>> corrections, should look like this:
>>>
>>>  
>>>   https://adwords.google.com/api/adwords/rm/v201509;>
>>>  
>>> ADD
>>> 
>>>Woopra Label: test-label-Id
>>>test-label-Id
>>>
>>>   
>>>  
>>> Woopra_Label-test-label-Id
>>> EQUALS
>>> true
>>>  
>>>   
>>>
>>> 
>>>  
>>>   
>>>
>>>
>>> Regards,
>>> Mike, AdWords API Team
>>>
>>>
>>> On Wednesday, December 16, 2015 at 2:28:48 AM UTC-5, ra...@woopra.com 

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Michael Cloonan (AdWords API Team)]

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 (significantly 
more complicated than what you're trying to do, but still demonstrates 
valid format):

   
  https://adwords.google.com/api/adwords/rm/v201509;>
 
ADD

   Users who checked out in November or December OR visited 
the checkout page with more than one item in their cart
   Expression based user list
   
  
 

   
  ecomm_pagetype
   
   EQUALS
   checkout


   
  cartsize
   
   GREATER_THAN
   1.0

 
  
  
 

   
  checkoutdate
   
   AFTER
   20141031


   
  checkoutdate
   
   BEFORE
   20150101

 
  
   

 
 
ADD

   Date rule user list created at 2015-12-18 09:52:45 
-0500
   Users who visited the site between 20141031 and 
20150331 and checked out in November or December OR visited the checkout page 
with more than one item in their cart
   
  
 

   
  ecomm_pagetype
   
   EQUALS
   checkout


   
  cartsize
   
   GREATER_THAN
   1.0

 
  
  
 

   
  checkoutdate
   
   AFTER
   20141031


   
  checkoutdate
   
   BEFORE
   20150101

 
  
   
   20141031
   20150331

 
  
   


One notable difference is that the operator element has a namespace 
defined. ns0 in this example request is defined on the Envelope as 
xmlns:ns0="https://adwords.google.com/api/adwords/cm/v201509;.

Try specifying the correct namespace on your operator to see if that 
resolves the problem.

Again, I apologize for getting it wrong at first; this is actually one of 
the only places in the API where xsi:type isn't used to differentiate.

Regards,
Mike, AdWords API Team

On Thursday, December 17, 2015 at 6:01:08 PM UTC-5, ra...@woopra.com wrote:
>
> 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 probably missing 
> an @Uses annotation while invoking public abstract com.google.ads.api.
> services.datax.userlists.UserListReturnValue com.google.ads.api.services.
> datax.adwordsuserlist.AdwordsUserListService.mutate(java.util.List) throws 
> com.google.ads.api.services.common.error.ApiException with params [[com.
> google.ads.api.services.datax.adwordsuserlist.v201509.jaxbgen.
> UserListOperation@47c87410]].
>
> I've seen your answers to a couple other posts about similar statements, 
> but the format of the xml requests in the answers in those threads are 
> different enough that I can't adapt them to my own.  Here is the body of my 
> request fixed to look like yours:
>
>
>   
>   https://adwords.google.com/api/adwords/rm/v201509;>
>  
> ADD
> 
>Woopra_test_label_Id
>test_label_Id
>
>   
>

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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/1999/REC-xml-names-19990114#ElementPrefixUnbound?ns0ns0:operator
 


This is my first time interacting with soap api so Im not sure if this 
could be related to my envelope being off or what.  Trying more things now. 
 

Oh here's the whole request btw in case you can spot something faster: 

Ok something is wrong because my xml formatter throws the same error so 
here it is raw:

http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;  xmlns:tns=
"https://adwords.google.com/api/adwords/rm/v201509; xmlns:jaxb=
"http://java.sun.com/xml/ns/jaxb; xmlns:cm=
"https://adwords.google.com/api/adwords/cm/v201509;
>https://adwords.google.com/api/adwords/rm/v201509; xmlns=
"https://adwords.google.com/api/adwords/rm/v201509;>
Woopra:AppConnect:getTrackersX
4579826953
https://adwords.google.com/api/adwords/rm/v201509;
>ADDWoopra_test_label_IdThis 
User List has been created to mirror the woopra label.
test_label_Id

Woopra_test_label_IdEQUALStrue






On Thursday, December 17, 2015 at 3:01:08 PM UTC-8, ra...@woopra.com wrote:
>
> 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 probably missing 
> an @Uses annotation while invoking public abstract com.google.ads.api.
> services.datax.userlists.UserListReturnValue com.google.ads.api.services.
> datax.adwordsuserlist.AdwordsUserListService.mutate(java.util.List) throws 
> com.google.ads.api.services.common.error.ApiException with params [[com.
> google.ads.api.services.datax.adwordsuserlist.v201509.jaxbgen.
> UserListOperation@47c87410]].
>
> I've seen your answers to a couple other posts about similar statements, 
> but the format of the xml requests in the answers in those threads are 
> different enough that I can't adapt them to my own.  Here is the body of my 
> request fixed to look like yours:
>
>
>   
>   https://adwords.google.com/api/adwords/rm/v201509;>
>  
> ADD
> 
>Woopra_test_label_Id
>test_label_Id
>
>   
>  
> 
>Woopra_test_label_Id
> 
> EQUALS
> true
>  
>   
>
> 
>  
>   
>
>
>
>
> thanks
> --Ralph
>
>
> On Wednesday, December 16, 2015 at 7:01:17 AM UTC-8, Michael Cloonan 
> (AdWords API Team) wrote:
>>
>> Hello,
>>
>> Rather than have a tag , you should have > xsi:type="ExpressionRuleUserList">. 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  altogether, rather than 
>> specifying it as nil.
>>
>> I am confused about why you're getting an error pointing to the operator, 
>> but hopefully cleaning up the operand to have the correct format by 
>> following the instructions above will fix it anyway.
>>
>> Just to be clear, the SOAP body you posted most recently, with 
>> corrections, should look like this:
>>
>>  
>>   https://adwords.google.com/api/adwords/rm/v201509;>
>>  
>> ADD
>> 
>>Woopra Label: test-label-Id
>>test-label-Id
>>
>>   
>>  
>> Woopra_Label-test-label-Id
>> EQUALS
>> true
>>  
>>   
>>
>> 
>>  
>>   
>>
>>
>> Regards,
>> Mike, AdWords API Team
>>
>>
>> On Wednesday, December 16, 2015 at 2:28:48 AM UTC-5, ra...@woopra.com 
>> wrote:
>>>
>>> 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 @ operations[0].operand` Which happens when I 
>>> try and wrap the operator/operand pair in another object like 
>>> "UserListOperation"
>>> So what this means to me is that the operand is not being read correctly.
>>>
>>> I'm not sure exactly what you meant by "You need to use the 
>>> ExpressionRuleUserList 

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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]

Here is the entire request again in case I'm missing something in the 
header or something in my account.


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; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
   
  https://adwords.google.com/api/adwords/rm/v201509; 
xmlns="https://adwords.google.com/api/adwords/rm/v201509;>
 Woopra:AppConnect:getTrackers
 X
 4579826953
  
   
   
  https://adwords.google.com/api/adwords/rm/v201509;>
 
ADD

   Woopra_test_label_Id
   test_label_Id
   
  
 

   
  Woopra_test_label_Id
   
   EQUALS
   true

 
  
   

 
  
   




So what could be wrong with the operator?  is "ADD" supposed to be a tag in 
itself?

--Ralph




-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/73271910-99b7-492a-a88b-fec5a71d8630%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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 probably missing an @Uses 
annotation while invoking public abstract com.google.ads.api.services.datax.
userlists.UserListReturnValue com.google.ads.api.services.datax.
adwordsuserlist.AdwordsUserListService.mutate(java.util.List) throws com.
google.ads.api.services.common.error.ApiException with params [[com.google.
ads.api.services.datax.adwordsuserlist.v201509.jaxbgen.
UserListOperation@47c87410]].

I've seen your answers to a couple other posts about similar statements, 
but the format of the xml requests in the answers in those threads are 
different enough that I can't adapt them to my own.  Here is the body of my 
request fixed to look like yours:


  
  https://adwords.google.com/api/adwords/rm/v201509;>
 
ADD

   Woopra_test_label_Id
   test_label_Id
   
  
 

   Woopra_test_label_Id

EQUALS
true
 
  
   

 
  
   



thanks
--Ralph


On Wednesday, December 16, 2015 at 7:01:17 AM UTC-8, Michael Cloonan 
(AdWords API Team) wrote:
>
> Hello,
>
> Rather than have a tag , you should have  xsi:type="ExpressionRuleUserList">. 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  altogether, rather than 
> specifying it as nil.
>
> I am confused about why you're getting an error pointing to the operator, 
> but hopefully cleaning up the operand to have the correct format by 
> following the instructions above will fix it anyway.
>
> Just to be clear, the SOAP body you posted most recently, with 
> corrections, should look like this:
>
>  
>   https://adwords.google.com/api/adwords/rm/v201509;>
>  
> ADD
> 
>Woopra Label: test-label-Id
>test-label-Id
>
>   
>  
> Woopra_Label-test-label-Id
> EQUALS
> true
>  
>   
>
> 
>  
>   
>
>
> Regards,
> Mike, AdWords API Team
>
>
> On Wednesday, December 16, 2015 at 2:28:48 AM UTC-5, ra...@woopra.com 
>  wrote:
>>
>> 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 @ operations[0].operand` Which happens when I 
>> try and wrap the operator/operand pair in another object like 
>> "UserListOperation"
>> So what this means to me is that the operand is not being read correctly.
>>
>> I'm not sure exactly what you meant by "You need to use the 
>> ExpressionRuleUserList 
>> 
>>  to 
>> add the RuleItem 
>> 
>>  instead 
>> of the RuleBasedUserList 
>> ."
>>  
>> Perhaps you can make your suggestions directly on the xml that I send so 
>> that i can figure out how to get that output from my soap client?  But 
>> since no matter what I do to the operand the error says the same thing 
>> about the operator, I feel like there is something wrong there.  should it 
>> be literally "" or "ADD" or what?  There isn't much room to play 
>> with the operator though...that's the flaw in my theory. :)
>>
>> Here's just the body of a cleaner attempt:
>>
>>  
>>   https://adwords.google.com/api/adwords/rm/v201509;>
>>  
>> ADD
>> 
>>
>>   
>>   Woopra Label: test-label-Id
>>   test-label-Id
>>   
>>  
>> 
>>
>>   Woopra_Label-test-label-Id
>>   EQUALS
>>   true
>>
>> 
>>  
>>   
>>
>> 
>> 

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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) wrote:
>
> Hello,
>
> Rather than have a tag , you should have  xsi:type="ExpressionRuleUserList">. 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  altogether, rather than 
> specifying it as nil.
>
> I am confused about why you're getting an error pointing to the operator, 
> but hopefully cleaning up the operand to have the correct format by 
> following the instructions above will fix it anyway.
>
> Just to be clear, the SOAP body you posted most recently, with 
> corrections, should look like this:
>
>  
>   https://adwords.google.com/api/adwords/rm/v201509;>
>  
> ADD
> 
>Woopra Label: test-label-Id
>test-label-Id
>
>   
>  
> Woopra_Label-test-label-Id
> EQUALS
> true
>  
>   
>
> 
>  
>   
>
>
> Regards,
> Mike, AdWords API Team
>
>
> On Wednesday, December 16, 2015 at 2:28:48 AM UTC-5, ra...@woopra.com 
>  wrote:
>>
>> 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 @ operations[0].operand` Which happens when I 
>> try and wrap the operator/operand pair in another object like 
>> "UserListOperation"
>> So what this means to me is that the operand is not being read correctly.
>>
>> I'm not sure exactly what you meant by "You need to use the 
>> ExpressionRuleUserList 
>> 
>>  to 
>> add the RuleItem 
>> 
>>  instead 
>> of the RuleBasedUserList 
>> ."
>>  
>> Perhaps you can make your suggestions directly on the xml that I send so 
>> that i can figure out how to get that output from my soap client?  But 
>> since no matter what I do to the operand the error says the same thing 
>> about the operator, I feel like there is something wrong there.  should it 
>> be literally "" or "ADD" or what?  There isn't much room to play 
>> with the operator though...that's the flaw in my theory. :)
>>
>> Here's just the body of a cleaner attempt:
>>
>>  
>>   https://adwords.google.com/api/adwords/rm/v201509;>
>>  
>> ADD
>> 
>>
>>   
>>   Woopra Label: test-label-Id
>>   test-label-Id
>>   
>>  
>> 
>>
>>   Woopra_Label-test-label-Id
>>   EQUALS
>>   true
>>
>> 
>>  
>>   
>>
>> 
>>  
>>   
>>
>>
>>
>>
>> Thanks again
>> --Ralph
>>
>>
>> On Tuesday, December 15, 2015 at 9:33:57 AM UTC-8, Umesh Dengale wrote:
>>>
>>> Hi Ralph,
>>>
>>> Thanks for providing the SOAP XML request. The RuleItem is associated 
>>> with DateSpecificRuleUserList 
>>> 
>>>  and ExpressionRuleUserList 
>>> .
>>>  
>>> You need to use the ExpressionRuleUserList 
>>> 
>>>  to 
>>> add the RuleItem 
>>> 
>>>  instead 
>>> of the RuleBasedUserList 
>>> 
>>> .
>>> I will submit a feature request for node/js client library.
>>>
>>> Thanks,
>>> Umesh, AdWords API Team.
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Umesh Dengale]

Hi Ralph,

Thanks for providing the SOAP XML request. The RuleItem is associated with 
DateSpecificRuleUserList 

 and ExpressionRuleUserList 
.
 
You need to use the ExpressionRuleUserList 

 to 
add the RuleItem 

 instead 
of the RuleBasedUserList 

.
I will submit a feature request for node/js client library.

Thanks,
Umesh, AdWords API Team.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/552f88b6-5eee-431e-b157-e2cba08bb291%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/ca055070-3c11-4002-acd8-322c9300623b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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 @ operations[0].operand` Which happens when I 
try and wrap the operator/operand pair in another object like 
"UserListOperation"
So what this means to me is that the operand is not being read correctly.

I'm not sure exactly what you meant by "You need to use the 
ExpressionRuleUserList 

 to 
add the RuleItem 

 instead 
of the RuleBasedUserList 
."
 
Perhaps you can make your suggestions directly on the xml that I send so 
that i can figure out how to get that output from my soap client?  But 
since no matter what I do to the operand the error says the same thing 
about the operator, I feel like there is something wrong there.  should it 
be literally "" or "ADD" or what?  There isn't much room to play 
with the operator though...that's the flaw in my theory. :)

Here's just the body of a cleaner attempt:

 
  https://adwords.google.com/api/adwords/rm/v201509;>
 
ADD

   
  
  Woopra Label: test-label-Id
  test-label-Id
  
 

   
  Woopra_Label-test-label-Id
  EQUALS
  true
   

 
  
   

 
  
   



Thanks again
--Ralph


On Tuesday, December 15, 2015 at 9:33:57 AM UTC-8, Umesh Dengale wrote:
>
> Hi Ralph,
>
> Thanks for providing the SOAP XML request. The RuleItem is associated with 
> DateSpecificRuleUserList 
> 
>  and ExpressionRuleUserList 
> .
>  
> You need to use the ExpressionRuleUserList 
> 
>  to 
> add the RuleItem 
> 
>  instead 
> of the RuleBasedUserList 
> 
> .
> I will submit a feature request for node/js client library.
>
> Thanks,
> Umesh, AdWords API Team.
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/aa2159c9-aaa9-4306-b496-3bd73cd19444%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[ralph]

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 
account.  Not sure what's going wrong It's probably the format of the 
operation because ZI get the same error if i send an empty object as the 
operation.  here's the request and response from my logs: (sorry about the 
format)

any help is appreciated. thanks

OUTGOING REQUEST:  http://schemas.xmlsoap.org/soap/envelope/; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
 xmlns:tns="https://adwords.google.com/api/adwords/rm/v201509; 
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb; 
xmlns:cm="https://adwords.google.com/api/adwords/cm/v201509;>https://adwords.google.com/api/adwords/rm/v201509; 
xmlns="https://adwords.google.com/api/adwords/rm/v201509;>XXXhttps://adwords.google.com/api/adwords/rm/v201509;>ADDWoopra Label: 
test-Label-IdThis User List has been created to mirror 
the woopra 
label.test-Label-IdRULE_BASEDWoopra_Label-test-Label-IdEQUALStrue


ERROR during listService.mutate():  { statusCode: 500,
  body: 'http://schemas.xmlsoap.org/soap/envelope/;>https://adwords.google.com/api/adwords/rm/v201509; 
xmlns="https://adwords.google.com/api/adwords/cm/v201509;>00052693bd9629000a42bf05e40XAdwordsUserListServicemutate1138soap:Server[OperatorError.OPERATOR_NOT_SUPPORTED
 
@ operations[0], RequiredError.REQUIRED @ 
operations[0].operator]https://adwords.google.com/api/adwords/cm/v201509; 
xmlns:ns2="https://adwords.google.com/api/adwords/rm/v201509;>[OperatorError.OPERATOR_NOT_SUPPORTED
 
@ operations[0], RequiredError.REQUIRED @ 
operations[0].operator]ApiExceptionhttp://www.w3.org/2001/XMLSchema-instance; 
xsi:type="OperatorError">operations[0]OperatorError.OPERATOR_NOT_SUPPORTEDOperatorErrorOPERATOR_NOT_SUPPORTEDhttp://www.w3.org/2001/XMLSchema-instance; 
xsi:type="RequiredError">operations[0].operatorRequiredError.REQUIREDRequiredErrorREQUIRED',

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/4273e404-c51d-49be-88ef-f3d5ec0be84b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ADD ExpressionRuleUserList OPERATION_NOT_SUPPORTED

[Umesh Dengale]

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 

 (e.g. StringRuleItem 

, DateRuleIte 

, NumberRuleItem 

 etc.) 
Please check out the AddRuleBasedUserLists 

 Java 
example code from the client library.

Thanks,
Umesh, AdWords API Team.

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/f5acdb4c-7c3d-42ca-b401-4a5fe299f32d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.