Add historical experience field values for a person in an account. Worth noting that this endpoint is purely additive, i.e. idempotent. It will also ignore field sets for fields that are not found under the account. Furthermore, if an experienceFieldValueId is provided, the corresponding value will be ignored. Multi-select fields accept several values by repeating the experienceFieldId, one entry per value; values already stored for the field are ignored.