Symptom
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
A user have more than one record saved if he has secondary assignments. Although these records are related, they could end up acting as they belong to different users.
These records belong to the same user, but one of them (chuber-1) is related to his secondary employment.
"Assembly Worker" would be the user's primary employment.
How to identify which one of the records belong to his secondary employment?
Environment
SuccessFactors, Integration Center
Resolution
When the record belongs to the user's secondary assignment, its information will be stored in the entity "SecondaryAssignments".
The record related to the user's primary assignment won't even have any information in the entity "SecondaryAssignments".
This can be used to filter out the records, or to properly identify them through another query or a calculated field.
Keywords
SuccessFactors, Integration Center, SecondaryAssignments, IsPrimary, other employments, Identifying secondary assignments of one user / employee, calculated field, OData API, User entity, EmpEmployment, specific, filter, calculated field, secondary position , KBA , LOD-SF-INT-INC-FWK , Integration Center UI Framework , LOD-SF-INT-INC , Integration Center , How To