GET and PATCH operations not working for TMF 632 Party/Organization Issue The record with a specific sys_id exists in the customer_account table, but retrieval (GET) and update (PATCH) operations for the TMF 632 Party/Organization API are failing with 'Resource not found' or 'Record not found' errors. The issue was observed on the instance, and similar behavior was noted in an out-of-the-box instance. Release All Releases Cause 1. The 'active' field is missing from the customer_account table on the instance, which is required by the Party Management API lookup logic. This field is contributed by the com.glide.domain.msp_extensions plugin, which is not installed on the instance.2. The absence of the 'active' field causes the API to return 'Resource not found' errors even when the record exists. Resolution 1. Verify the presence of the 'active' field on the customer_account table. If missing, proceed to the next step.2. Install the com.glide.domain.msp_extensions plugin on the instance, as this plugin contributes the 'active' field required by the Party Management API logic.3. Test the GET and PATCH operations again after the plugin installation to confirm resolution.