Using service name (EMPLOYEE) in Where Clause

I use the Resource Query in a few different processflows but have never seen the format that your are using (!CDATA[({EMPLOYEE}=)]. With my queries it shows a And then >]]>

Jeff - I left some of the brackets out because they will cause the information not to show on the post/emails - but you are correct there would be two end brackets =)]]
I'm looking for what goes inside the {} to indicate this is the service name Employee for the where clause.
Thanks,
Karen

Yeap - the website changed the post - I've removed all the great than and less than signs this time

WHERE ![CDATA[({EMPLOYEE}=!Query4690_EMPLOYEE)]] /WHERE

Are you using the RMQuery node in ProcessFlow Integrator? When I build the queries I've never seen a WHERE Clause in the query it is just the two sets of tags that I added above. The first set of tags indicate what field I am mapping to and the second set of tags indicate the value I am looking to match on. They are all working for me fine.
Looking at the last response do you have the !Query4690_EMPLOYEE inside greater than and less than signs?

I tried using the code that came out of the builder and that didn't work either. It pretty much ignored it.

The where clause I'm using is from the PF Developer manual example

There is a set of greater than/less than signs around both Where keys words and before the ! and after the ]]
I'm not getting a syntax error on that - if I use {ID} the where works, if I use {EMPLOYEE} it does not
If I use the VALUE statements in the body of the "select", it ignores them
Thanks,
Karen

In the select, I am select ID, and then Company and Employee. If I click on the node after the Resource QUery, the only field listed is the ID - is that normal?

THanks,
Karen

We may have a version problem - just upgraded the ENV to 9.0.1.9 and appearently didn't upgrade PF - hopefully that will resolve the issue

Thanks,
Karen

I don't know if it was the version mismatch or user error or a combination of both, but the query is working correctly this morning built from the builder using the value clauses as noted by JeffR and not an inserted Where clause as shown in the manual.

However, the test console message in the designer when it doesn't find a match is "Invalid Where clause", which would lead you to believe there is something wrong with your query; kind of a bogus message.

Thanks Jeff

Karen