SuccessFactors Connector – EmpJob attributes no longer populating (works in Prod, fails in lower env)

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi everyone,

I’m running into a strange issue with the SuccessFactors connector and hoping someone in the community has seen this before.

Background

We have a SuccessFactors source that was previously working correctly and aggregating data without issues. At some point, it stopped populating data from the EmpJob object, even though:

  • The same configuration works fine in Production

  • There are no meaningful configuration differences other than the target environment/endpoint

  • The SuccessFactors team has confirmed that the data exists on their side

Account-level data is still being pulled correctly — the issue seems isolated to EmpJob-related attributes.

What’s happening

  • Attributes sourced from EmpJob (e.g. contractType, countryOfCompany, costCenter, etc.) are coming in as empty / null

  • These attributes are defined in the schema as:

    EmpJob.contractType
EmpJob.countryOfCompany
EmpJob.costCenter

  • Aggregation completes without errors, but the EmpJob fields are simply not populated

What I tested

To rule out data and API issues:

  • Ran a direct OData API call to SuccessFactors:

    /odata/v2/EmpJob?$filter=userId eq '<USERID>'

  • The response does return the expected data for all fields (contractType, countryOfCompany, costCenter, etc.)

  • SuccessFactors team confirmed no permission, data, or configuration issues on their side

Things that look odd

  • Same connector configuration works in Prod, but not in this lower environment

  • No recent schema changes on our side

  • No connector errors or warnings specifically pointing to EmpJob

Questions for the community

  • Has anyone seen a scenario where EmpJob data is available via direct API calls, but not populated through the SailPoint SuccessFactors connector?

  • What else should I be checking from a SailPoint side?

  • Any logs, connector settings, schema refresh steps, or validation techniques that have helped in similar situations?

Any insights, or pointers would be very helpful. Thanks in advance!

-– Juan

2

Hello Juan,

Could you please check if the below are the same between Prod & the lower env:

  • Aggregation Query Filter (docs)

  • Time Zone setting on the SailPoint source (docs)

  • Connector version

Any difference in these could be the reason behind the issue you’re seeing.

3

Thanks, Harish. I reviewed the issue and confirmed it was caused by a schema change, specifically a case difference in the attribute name (userId → UserId). I didn’t notice it initially since it was only a casing change.