Aron's Tech Blog

So I found myself having to create an export for only UDF’s and had to code it for the type coming out of the custom dictionary so that if it was a string it would output just the field and if it was a date it would apply a TO_CHAR function along with a date specification. As I hang my head in shame I did it in Excel because I didn’t have time to write the Python version of it and inadvertently misspelled field.

To make a long story short the GUI threw an error saying this is the list of expected elements, I’m sure this is somewhere in an XSD but it’s now here for reference:

read more »

Sometimes you will notice some strange things dealing with time when using TCC and the LRD (last run date). You’ll find that even your export is scheduled for every 10 minutes you’re not getting the people that you just switched to the conditions of the filters. This is especially infuriating when you’re just bringing something to fruition and just testing.

The reason for this is that TCC by default is using [CURRENT_TIME] – 5 minutes for the LRD.

You can set this by adding a line to the *_sq.xml file advanced options with a value lrd.filtering.minute.adjustment.zone with the value being time in minutes.

This is documented on the MOS under Doc ID 1590569.1

I never thought that this would work but it seems to run just fine, putting it here for future reference. This returns candidates numbers that have an application to a requisition that’s posted, used for a T-XML candidate attachment export.

<quer:filtering xmlns:quer="http://www.taleo.com/ws/integration/query">
  <quer:includedIn>
    <quer:field path="Number"/>
    <quer:query projectedClass="Application" alias="sqMotives" preventDuplicates="true" pagingsize="1">
      <quer:subQueries/>
      <quer:projections>
        <quer:projection>
          <quer:field path="Candidate,Number"/>
        </quer:projection>
      </quer:projections>
      <quer:filterings>
        <quer:filtering>
          <quer:includedIn>
            <quer:field path="Applications,Requisition,Number"/>
            <quer:query projectedClass="SourcingRequest" alias="sqMotives" preventDuplicates="true" pagingsize="1">
              <quer:subQueries/>
              <quer:projections>
                <quer:projection>
                  <quer:field path="Requisition,Number"/>
                </quer:projection>
              </quer:projections>
              <quer:filterings>
                <quer:filtering>
                  <quer:equal>
                    <quer:field path="SourcingRequestStatus,Number"/>
                    <quer:string>2</quer:string>
                  </quer:equal>
                </quer:filtering>
              </quer:filterings>
            </quer:query>
          </quer:includedIn>
        </quer:filtering>
      </quer:filterings>
    </quer:query>
  </quer:includedIn>
</quer:filtering>

This post is to consolidate the information about the required update of TCC to version 17.x

TCC: Does TCC Need To Be Upgraded When A Zone Is Upgraded? (Doc ID 2086226.1)
This article addresses the question of whether TCC needs to be upgraded when a zone is upgraded.

read more »

I’ve been driven crazy a few times trying to figure out which code goes to which language so here it is for future reference:
read more »

So I was trying to do a replace null on two date fields and render it toChar yyyy-MM-dd and it kept giving me the lovely ‘SAX parsing error’, looking in the profiler I get this reason:
Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]
After rearranging the order of the toChar and replaceNull and still getting the same thing, I finally stumbled on the answer which was to declare the projection as a toChar by adding:
projectedField=”RuntimeString:toChar”
To the projection attributes.
I’m not 100% sure why this has to be done but it fixed the issue so figured I’d post it here.