enhancement request to support "upsert" function import from SAP SuccessFactors API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 268
- Forks
- 100
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
Can you please consider a new enhancement to support "upsert" function import coming from SAP SuccessFactors API?
Metadata:
FunctionImport< Name="upsert" ReturnType="Collection(SFOData.UpsertResult)" EntitySet="UpsertResult" m:HttpMethod="POST" sap:support-payload="true" >/FunctionImport<"
Example payload:
Method: POST https://api2preview.sapsf.eu/odata/v2/upsert
Body: {
"__metadata": {
"uri": "FormPMReviewContentDetail(formContentId=169736L,formDataId=32107L)",
"type": "SFOData.FormPMReviewContentDetail"
},
"competencySections": [
{
"__metadata": {
"uri": "FormCompetencySection(formContentId=169736L,formDataId=32107L,sectionIndex=1)",
"type": "SFOData.FormCompetencySection"
},
"competencies": [
{
"__metadata": {
"uri": "FormCompetency(formContentId=169736L,formDataId=32107L,itemId=13550L,sectionIndex=1)",
"type": "SFOData.FormCompetency"
},
"officialRating": {
"__metadata": {
"uri": "FormUserRatingComment(formContentId=169736L,formDataId=32107L,itemId=13550L,ratingType='official',sectionIndex=1,userId='admin')",
"type": "SFOData.FormUserRatingComment"
},
"ratingKey": "wf_sect_1__c13550_r",
"rating": "1.0"
}
}
]
}
]
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides SAP SuccessFactors function-import metadata, the POST endpoint, and a nested example payload, but names no repository files or tests. Start by tracing how function imports and POST requests are currently handled, then compare that path with the supplied upsert metadata. Done means the upsert import accepts the shown request shape and returns its documented result type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100