TCC（Windows）导出Taleo职位申请：Evergreen职位布尔字段查询报错求助

Let’s break down the issues with your TCC query step by step—these are common pitfalls when working with Taleo’s query syntax, especially around field paths, data types, and XML structure:

1. Incorrect Field Path Formatting #

Taleo’s TCC uses dot notation for nested field paths, not commas. Additionally, internal field identifiers rarely include spaces. Your current path JobInformation,Evergreen Req Number is invalid. You’ll need to use the exact internal field name for your Taleo instance (likely something like JobInformation.EvergreenReqNumber or JobInformation.EvergreenRequisitionNumber—confirm this via your Taleo metadata or instance’s field reference).

2. Mismatched Filter Logic for Boolean Fields #

Evergreen requisition status is almost always a boolean (true/false) field, not an integer. Using <greaterThan> with an integer 1 doesn’t align with how this field is stored. Instead, use an <equal> filter with a boolean value:

<equal>
  <field path="JobInformation.EvergreenReqNumber"/>
  <boolean>true</boolean>
</equal>

If your instance does store this as an integer (1 for evergreen, 0 otherwise), the <greaterThan> logic could work—but only after fixing the field path first.

3. Projection Issues #

Your current projection returns the string "true" for every record, which isn’t useful for identifying evergreen status. To add a proper boolean flag:

• Either project the actual evergreen field directly:

  <projection>
    <field path="JobInformation.EvergreenReqNumber"/>
  </projection>
  

• Or use a conditional expression to return a custom flag (if you need to transform the value):

  <projection>
    <conditional>
      <equal>
        <field path="JobInformation.EvergreenReqNumber"/>
        <boolean>true</boolean>
      </equal>
      <boolean>true</boolean>
      <boolean>false</boolean>
    </conditional>
  </projection>
  

Also, the <quer:string> element requires the quer namespace to be declared in the root <query> tag—missing this can cause parsing errors.

4. Missing Namespace Declaration #

TCC queries rely on proper XML namespaces to validate elements. Add the required namespace to your root query element:

<query alias="testEvergreen" projectedClass="Requisition" xmlns:quer="http://www.taleo.com/ws/integration/query">

Corrected Query Example #

Here’s a fully revised version of your query incorporating these fixes:

<query alias="testEvergreen" projectedClass="Requisition" xmlns:quer="http://www.taleo.com/ws/integration/query">
  <projections>
    <!-- Project the raw evergreen status field -->
    <projection>
      <field path="JobInformation.EvergreenReqNumber"/>
    </projection>
    <!-- Optional: Project a custom boolean flag for clarity -->
    <projection>
      <conditional>
        <equal>
          <field path="JobInformation.EvergreenReqNumber"/>
          <boolean>true</boolean>
        </equal>
        <boolean>true</boolean>
        <boolean>false</boolean>
      </conditional>
    </projection>
  </projections>
  <filterings>
    <filtering>
      <equal>
        <field path="JobInformation.EvergreenReqNumber"/>
        <boolean>true</boolean>
      </equal>
    </filtering>
  </filterings>
</query>

Bonus Tip #

If even documentation examples are failing, double-check your TCC client’s connection to the correct Taleo instance and verify you have permissions to access the Requisition object and its JobInformation fields. Permission issues often masquerade as syntax errors in TCC’s editor.

内容的提问来源于stack exchange，提问作者u07ch