2443143 - List of Odata API Entities that do not support a direct Query

This is a reference list of Odata API entities that don't allow a direct Query operation.

Successfactors Odata API

Integration Center

This is due to:

1) Presence of mandatory filterable fields to be included in the query request.

2) The entity is focussed on returning data for a single user or a single form or template.

3) The entity is only used to fetch the metadata to build payload to another entity. Therefore, you may not directly use these entities in API integrations.

Example - Template entities of RCM. They are used to build payload to “JobRequisition” entity.

Form360RaterSection
AssignTeamGoal
Form360ReviewContentDetail
FormCompetency
FormCompetencySection
FormCustomElement
PersonKey
FormCustomElementListValueDGExpression
FormCustomSection
DGFieldOperator
FormItemConfiguration
FormPMReviewContentDetail
DGFieldValue
FormRaterListSection
DGFilter
FormSectionConfiguration
DGPeoplePool
FormSignatureSection
EPProfilePortlet
EPProfileUserInfoPortlet
EPProfileView
EPPublicProfile
EmpCompensationCalculated
EmpCompensationGroupSumCalculated
EmpTimeAccountBalance
GoalPlanState
InlineResult
MDFEnumValue
MDFLocalizedValue
NomineeHistory
PersonEmpTerminationInfo
SimpleDevGoal
Successor
SuccessStoreContent
SuccessStoreContentBlob
SimpleGoal
ThemeTemplate
UpsertResult
UserPermissions
WorkflowAllowedActionList
DevGoalTarget_*
GoalMetricLookup_*
GoalMetricLookupPermission_*
GoalMetricLookup_*
GoalMilestonePermission_*
GoalMilestone_*
GoalPermission_*
GoalTaskPermission_*
GoalTask_*
GoalTarget_*
GoalTargetPermission_*
JobReqTemplate_*
JobOfferTemplate_*
JobApplicationTemplate_*

Please do not use these entities as a starting point in API/Web service integrations.

Unsupported Entities for integrations. , KBA , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT-INC , Integration Center , How To