This post was originally published on this site
When implementing LinkedIn Recruiter System Connect (RSC) for the first time, you notice that some field mappings have hardcoded fields from SuccessFactors Recruiting, which cannot be modified to other fields. This happens because there’s backend mapping between LinkedIn and SuccessFactors for certain fields. As LinkedIn expects to receive certain values for specific fields, an internal mapping defines how each value is sent. As a result, it is not possible to change the mapping to other Recruiting fields.
You can find the full list of field mappings and whether each one is editable here: Field Mapping Information
For example, industries and employmentStatus from LinkedIn are mapping to industry and classificationType accordingly in Recruiting, and the mapping cannot be changed.
This requirement can create implementation challenges, as some fields linked to these mappings are not used by customers, and they may have other standard or custom fields where the same information is stored.
This blog explains how to move the existing data into the fields required for the mapping using Integration Center. For example, if a customer does not use the employmentStatus standard field but has another field with the same information, they must still map and fill employmentStatus to implement LinkedIn Recruiter System Connect (RSC).
NOTES:
This integration needs experience with Integration Center and Recruiting configuration, and it is