Aron's Tech Blog

Ran across this and it took me a while because of the dot notation that they are using in the path, seems you can just ignore it and use it as part of the path.

<quer:filtering xmlns:quer="http://www.taleo.com/ws/integration/query">
<quer:or>
<quer:equal>
<quer:field path="Candidate,History,ApplicationTrackingHistoryItem.CreationDate"/>
<quer:query projectedClass="Application" alias="histItemSubQuery">
<quer:projections>
<quer:projection>
<quer:maximum>
<quer:field path="Candidate,History,ApplicationTrackingHistoryItem.CreationDate"/>
</quer:maximum>
</quer:projection>
</quer:projections>
<quer:filterings>
<quer:filtering>
<quer:equal>
<quer:field ownerQuery="histItemSubQuery" path="Number"/>
<quer:field ownerQuery="NewHire" path="Number"/>
</quer:equal>
</quer:filtering>
</quer:filterings>
</quer:query>
</quer:equal>
<quer:isNull>
<quer:field path="Candidate,History,ApplicationTrackingHistoryItem.CreationDate"/>
</quer:isNull>
</quer:or>
</quer:filtering>

I recently came upon a situation where we needed the start date but because the offer module not being used, we needed to get it from the history.

Here is where it lives:
Candidate,History,ApplicationTrackingHistoryItem.Detail

and you have to filter on the event code:
Candidate,History,ApplicationTrackingHistoryItem.Event,Code

There are times that you want to just return some text in an export column. This comes in handy when let’s say you’re exporting job templates and need to put in a new code. In any case if you need it you can use this snippet to do so:

<quer:projection alias="Test" xmlns:quer="http://www.taleo.com/ws/integration/query">
 <quer:string>ThisIsIt</quer:string>
</quer:projection>

I got asked today if it was possible to return just those users who had one group and that group was the main group.  I wasn’t able (yet) to use the count function in the filter so what I did was this:

I returned UserNo, keyCount (count of UserAccount,Groups,Name).
I added a filter to equal the string main group.
In the resultant file, the users who had a count of 1 would only be in the main group.

This isn’t ideal but it does give a list of those who are only in the main group with a little massaging.  Attached it the export file for this process.

UserExport_sq

Okay, the last one I published doesn’t have the cut and paste ability for the complex filter, so here it is:

<quer:filtering xmlns:quer="http://www.taleo.com/ws/integration/query">
 <quer:or>
 <quer:equal>
 <quer:field path="UserAccount,Groups,Name"/>
 <quer:string>usmagn</quer:string>
 </quer:equal>
 <quer:equal>
 <quer:field path="UserAccount,Groups,Name"/>
 <quer:string>uspacs</quer:string>
 </quer:equal>
 </quer:or>
</quer:filtering>

One of the most general errors you will encounter in TCC is the dreaded SAX parsing error.  It happens often and gives you no clue as to what went wrong.

The way to get it to give you the details of the error is to go into the post processing tab of the config file and uncheck the ‘Fail on export error’ checkbox.  While this won’t fix the error it will now return the error (more specifically the field that’s causing the error) in the response file.