I think the function `ParsePartialFromArray()` is what you're looking for.
Note that generally you shouldn't rely on this too heavily though; if you serialize such a message and send it to another end point they will be expecting all required fields to be set and may correctly parse fail; the intent of ParsePartial is that if you're going to serialize it back out you should set the required fields first.
Broadly, required fields were removed from proto3 because they cause a lot of problems, including that they very hard to remove a required field when you realize you don't need it; eg you may think `string username` is required today but when you realize you want a `int64 userid` instead it's very hard to make that transition if you marked username as required. You may want to consider migrating your fields off of being marked required as a long term solution.