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.
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>
In looking at the services, I selected candidate as the first one to test. I’m using Soap UI for my testing purposes. I’ve created a project utilizing the Think Talent partner zone candidate service by entering the copied URL for the WSDL. Here is what I’m presented with:
To get a list of services you must log onto the zone that you are trying to utilize
https://hostname.taleo.net/enterprise/soap
You should see something like this:
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.
This applies to the encoding of the file that TCC produces for the response. Let’s say you need it in something other that UTF-8. In this case we’d like to see it in ISO-8859-1. First you have to specify the response encoding in the configuration general tab:
If you were to save and run at this point, it will fail. In the manual you will find this on the subject:
The Encoding states the way the file is encoded. The Taleo environment only supports UTF-8 encoding.
Conversion is available in the Pre- and post-processing steps. -p55 TCC-13B-UserManual
This means that there needs to be a post processing step to change the encoding, fortunately it’s a pre-populated function called ‘Convert Encoding’. Simply add that into the post processing step after the Strip SOAP step as shown below and you’re good to go.
This complex filter ensures that you are pulling the most recent offer information with the new hire.
<quer:filtering xmlns:quer="http://www.taleo.com/ws/integration/query"> <quer:equal> <quer:field path="Offers"/> <quer:query projectedClass="Offer" alias="My_Offer_Subquery"> <quer:projections> <quer:projection alias="MaxOffer"> <quer:maximum> <quer:field path="Offers,Number"/> </quer:maximum> </quer:projection> </quer:projections> <quer:filterings> <quer:filtering> <quer:equal> <quer:field path="Application,Offers"/> <quer:field ownerQuery="NewHire" path="Offers,Number"/> </quer:equal> </quer:filtering> </quer:filterings> </quer:query> </quer:equal> </quer:filtering>
