• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Using service name (EMPLOYEE) in Where Clause

 9 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/19/2012 1:04 PM
I am trying to do a resource query where the service name/identity Employee equals the HR11 Employee number

If the where clause looks like this - it works
![CDATA[({ID}=)]

But what I really want to do is match against the Employee Identity - this does not appear to work
![CDATA[({EMPLOYEE}=)]

serviceName="testhcm_EMPLOYEE">
In reading other posts, it appears that this can be done, but I couldn't find any examples.

TIA,
Karen 
JeffR
Advanced Member Send Private Message
Posts: 22
Advanced Member
4/19/2012 4:08 PM
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 >]]>
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/19/2012 4:28 PM
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
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/19/2012 4:32 PM
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
JeffR
Advanced Member Send Private Message
Posts: 22
Advanced Member
4/19/2012 4:46 PM
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?
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/19/2012 5:26 PM
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
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/19/2012 5:30 PM
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
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/19/2012 5:32 PM
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
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/19/2012 7:00 PM
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
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
4/20/2012 12:23 PM
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