Updating Table-Data Details for an Existing Revisable Regulatory Submission
To update the attributes of a table-data type for an existing revisable regulatory submission, the regulatory submission must be the latest revision (version) and must be checked out. To update table data details, you must have Modify permissions to the regulatory submission. Using this request, you can also update the same attributes from both the parent type and child type of a table data in a single call.
 
The table data ID specified must be the ID that is retrieved for the checked-out version of the revisable regulatory submission.
The attributes that are defined with a "Required" constraint in Windchill must be specified.
Each table data attribute must adhere to its defined:
Attribute constraints
Cascading attribute rules
The following example shows you how to update a String type attribute for the TestType table data for a revisable regulatory submission. Use the following PATCH URI with the request body.
URI
PATCH /Windchill/servlet/odata/RegMstr/RegSubmission2('OR:com.ptc.qualitymanagement.regmstr.AdverseEventRegulatorySubmission:272722')/TableData('OR:com.ptc.tabledata.TableData:283972')
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"@odata.type": "#PTC.RegMstr.TestType",
"TDString": "test123"
}
Example: Updating the Same Attribute from Both the Parent Type and Child Type of a Table Data
The following example shows you how to update the same attribute from both the parent type and child type of a table data for a revisable regulatory submission. This example shows you how to update a String type attribute for the TestType table data and an Integer type attribute available in both the TestType table data and its parent type table data. Use the following PATCH URI with the request body.
URI
PATCH /Windchill/servlet/odata/RegMstr/RegSubmission2('OR:com.ptc.qualitymanagement.regmstr.AdverseEventRegulatorySubmission:272722')/TableData('OR:com.ptc.tabledata.TableData:283972')
Request Headers
Content-Type: application/json
CSRF_NONCE: <Use the value from Fetch NONCE example>
Request Body
{
"@odata.type": "#PTC.RegMstr.TestType",
"TDString": "test125",
"TDInteger": 124
}