CandidateSelection functionality in Data Services

[Former Member]

When running a Match transform only using the CandidateSelection option, is there a way to get the candidates primary key from the database appended to the lookup results with the same primary key field from the lookup? I've only been able to get it appended to a completely different field. I need them in the same field for the next transform and really don't want to be forced to add a Query in between.

In my case, the primary key from the database is called PRS_KEY. In my column mappings, I've tried mapping the returned PRS_KEY to a CANDIDATE_SELECTION output field and back to the PRS_KEY as well. In other words I have two column mappings defined.

But for my one candidate returned, the CANDIDATE_SELECTION field contains the key I want but the PRS_KEY is null for the candidate. For my lookkup rows, they all contain Nulls in CANDIDATE_SELECTION and have their original key in PRS_KEY.

I really need all of the keys from all of the rows returned in thePRS_KEY or some other field.

Thanks

[Former Member]

Chuck,

You do not need two column mappings. For your requirement, mapping the DB Column PRS_KEY to (input) Field PRS_KEY (assuming that is the name of the input field you are mapping back to) should work. Remove the additional mapping CandidateSelect_PRS_KEY and you will get the right results.

Abhiram

[Former Member]

Thanks Abhiram! I took out the CandidateSelect mapping and the transform is now correctly putting the key in the correct place.

Though I'm not sure why. The reason I wanted the PRS_ID key from the database in both the CandidateSelect field and the PRS_KEY was for downstream debugging. So figured I could handle this request with 2 column mappings.

Is there a rule in the transform that doesn't allow for that or something related to using the generated CandidateSelect output?

Just curious.

Thanks again!