Symptom
You created a custom OData service on the busines object ServiceRequest and on the entity type ServiceRequestUsedAddress. You performed a POST successfully and you received the status 201 - created. But there is no response payload.
Environment
SAP Cloud for Customer
Reproducing the Issue
- Open Postman
- Select Post as method
- Enter the following URL https://myXXXXXX.crm.ondemand.com/sap/c4c/odata/cust/v1/YYY/ServiceRequestUsedAddressCollection (where XXXXXX is the system URL and YYY is the name of custom OData service)
- Click on Execute
Cause
The entity type ServiceRequestUsedAddress is based on the USED_ADDRESS BO which has a special implementation. It is a transient BO and no instances are persisted for the same in the database.
Resolution
- When a POST operation is successfully done on the above entity type, there will be no response payload. It is the expected system behavior.
- If you wish to view the created ServiceRequestUsedAddress instance, then it can be accessed via navigation from its parent entity type instance: https://myXXXXXX.crm.ondemand.com//sap/c4c/odata/cust/v1/YYY/ServiceRequestPartyCollection('ObjectID')/ServiceRequestUsedAddress.
Keywords
ServiceRequestUsedAddressCollection, no resonse payload, POST call, ServiceRequestUsedAddress, , KBA , AP-RC-ODF , OData framework (C4C Only) , Problem
Product
SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions