How many entities do not support simple PATCH of 'status' and 'state' codes?

Question

For example: to set an account record to inactive you need to send the request to

PATCH https://<hostname>/api/data/v9.0/accounts(000-000-0000-0000)

with the body

{
  "statecode": 1,
  "statuscode": 2
}

but it does not work with the opportunity entity. To mark it Won or Lost you should send a request that differs from the above one. I want to know how many entities do not support a simple request to change their state.

Answer 1

From top of my head, I remember these below scenarios have special dialog and there’s an extra entity where more details will be captured on status change.

1. Opportunity close - this is an activity type
2. Case resolution
3. Quote close

For these scenarios, instead of doing PATCH of statecode/statuscode, we have functions/actions to invoke using sdk/web api. Read more

That being said, I never seen a list or consolidation in the internet for these exceptions. Atleast I gave you a starting point, since there may be more. System user entity is different too. Btw, what are you trying to achieve?