Taleo Web Services Export Has The Wrong Attachment In The Results (Filtering vs Projection Filtering)
(Doc ID 2691703.1)
Last updated on DECEMBER 07, 2022
Applies to:
Oracle Taleo Platform Cloud Service - Connect - Version 20B and laterOracle Taleo Recruiting Cloud Service - Version 19A and later
Information in this document applies to any platform.
Symptoms
A Taleo WebServices API attachment export with filters on the attachment comment does not return the expected attachment. The same problem does not occur when using TCC with simple filters on the comment for the export.
Scenario: Candidate number 123 has the following attachments:
FileName Comment
Attachment01 Doc01
Attachment02 AdditionalInfo
Attachment03 Platypus
A Taleo webservices API call to export attachment filename, based on class "ApplicationTrackingAttachFileItem" has the following filters:
<quer:projectionFilterings/>
<quer:filterings>
<quer:filtering>
<quer:equal>
<quer:field path="Candidate,Number"/>
<quer:string>12805</quer:string>
</quer:equal>
</quer:filtering>
<quer:filtering>
<quer:equal>
<quer:field path="AttachedFile,Comment"/>
<quer:string>Platypus</quer:string>
</quer:equal>
</quer:filtering>
<quer:filtering>
<quer:equal>
<quer:field path="CommentText"/>
<quer:string>Platypus</quer:string>
</quer:equal>
</quer:filtering>
</quer:filterings>
The above filtering has Attachment01 in the results instead of the expected Attachment03.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |