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?