AnsweredAssumed Answered

Profile mapping fail with Successfactors compound employee

Question asked by GarethHughes8951 on Oct 26, 2016
Latest reply on Apr 17, 2017 by jclark1648648

I'm just getting into Successfactors. We have a test instance running.

I've managed to build a Query for CompoundEmployee and get 3 results back.

I then pumped that data into a Map with the SuccessFactors CompoundEmployee QUERY Response on the left of the Map

 

The map fails with the usual complaint that the profile is wrong. It's definitely not and I've definitely not used the wrong profile etc.

So how do I get any further in fixing this? Do I need a support ticket? Is there any logging behind the scenes on the Atom that will tell me which field it is stuck on?

 

I'm suspicious because the profile doesn't have the Id field or the execution_timestamp field. But everything else looks ok.

Or is it a namespace issue?

 

 

 

I'm getting back the absolute minimum

 

<CompoundEmployee>
<id>53</id>
<person xmlns="urn:sfobject.sfapi.successfactors.com" xmlns:ns2="urn:fault.sfapi.successfactors.com">
<country_of_birth>USA</country_of_birth>
<created_by>admindlr</created_by>
<created_on_timestamp>2015-01-08T19:31:23.000Z</created_on_timestamp>
<date_of_birth>1966-09-22</date_of_birth>
<last_modified_by>admindlr</last_modified_by>
<last_modified_on>2015-09-06T21:04:37.000Z</last_modified_on>
<person_id>53</person_id>
<person_id_external>80279</person_id_external>
</person>
<execution_timestamp xmlns="urn:sfobject.sfapi.successfactors.com" xmlns:ns2="urn:fault.sfapi.successfactors.com">2016-10-26T16:36:35.000Z</execution_timestamp>
<version_id xmlns="urn:sfobject.sfapi.successfactors.com" xmlns:ns2="urn:fault.sfapi.successfactors.com">1608P0</version_id>
</CompoundEmployee>

 

Many thanks

Outcomes