Symptom
When bulking update Custom Table Entries using a Patch request, PATCH api/custom-table/v1/customTables/<Custom Table Name>/entries, CPQ returns different response body in case of failures during an Update or Insert activity.
Environment
SAP SALES CLOUD CPQ
Reproducing the Issue
- Perform a PATCH api/custom-table/v1/customTables/<Custom Table Name>/entries for following scenarios:
- Insert new entries in the Table
- In case 1 or more entries contains an error, response body will contain only the information regarding the first error and no entry will be inserted
- Update entries in the Table
- In case 1 or more entries contains an error, response body will show each error and return OK for the updated information
- Insert new entries in the Table
- For both scenarios, API will return status 202. Error regarding information of the payload will be shown in the Response Body.
Cause
Expected Behavior.
Resolution
- For the insert operation, if any of the entries are invalid, the entire process will fail, no data will be written, and an error will be returned for the first invalid entry
- For the update operation, it will process all entries, updating the valid ones, while ignoring the invalid ones, and it will return a response for each entry.
See Also
Keywords
Custom Table API, API, Entries, Patch, Insert, Update, Error Handling, Expected Behavior, Response Body, CPQ , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Bug Filed
Product
SAP CPQ 2024
SAP Knowledge Base Article - Public