Constellation DX API: "Error_Invalid_Inputs_content" with one pageInstruction, but works with two

I’m calling the DX Patch API from an Angular front end (Constellation, Pega [26 infinity]) to update a nested page list, three levels deep.

What fails: I send one `pageInstructions` entry with an `UPDATE` on row 1 of the list. Row 1 already exists on the case. Pega returns a bad request: “One or more inputs are invalid” with the message `Error_Invalid_Inputs_content`. No field name is given in the error.

What works: I send the same first instruction plus a second `UPDATE` for row 2. This call succeeds.

What I’ve found:

- Both calls use the same URL (same case, and action).

- The first instruction has the same structure and properties in both calls. Only the values differ.

- “Check field security” is what fails in the single-instruction case.

- Many properties in the payload are not on the view for this action.

Questions:

1. Why does the same view and property set pass field security with multiple instructions but fail with one? Is the check applied differently, or are unpermitted properties silently ignored?

2. For properties not on the view, should I add them to the view or limit the payload to the view’s properties?

The issue is most likely caused by properties in the DX API request that are not allowed by the current action view. In Pega Constellation, field security validates submitted properties against the fields defined in the view. Update your Angular payload to include only properties configured in that action view. For the nested Page List, use a single pageInstructions entry with UPDATE, the correct target path, and listIndex: 1. Include only the required, permitted properties inside the content object. Remove any additional properties that are not part of the view. The successful request with two instructions does not guarantee that all submitted fields are permitted. Use Pega Tracer to verify the field security validation and test the single-row update again. This should resolve the error if unauthorized fields are causing the failure