Symptom
When using this patch request: PATCH/api/custom-table/v1/customTables/{tableName} customer reported an issue where when they pass an API call to update an existing custom table, it is not working as expected and the patch request creates a new custom table instead of updating it.
Environment
SAP SALES CLOUD CPQ
Cause
Users did not mention keyword "keys" inside the context with column name.
Resolution
User should mention keyword "Keys" inside the context of the body while passing this patch request - PATCH/api/custom-table/v1/customTables/{tableName}
In addition, if you wish to update multiple columns at the same time, you can mention two primary column names.
For example, if you wish to update the value based on the state and city, you can mention multiple state and city names inside the keys .
Example:
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
See Also
Keywords
patch request, how to pass patch request to update the custom table?, update custom table, Patch REST API, how to update custom table through patch REST API, modify data in custom table, edit data in custom table. , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , How To