When the user saves a single phone number for a Health Care Professional (HCP) or Health Care Organization (HCO) Profile, why does Network populate the value into the phone_2__v field? The user expects it to be populated in the phone_1__v field on the profile.
This behavior is working as designed. As there is only one phone field populated on the profile, the user may expect that the field which currently contains the value is phone_1__v. However, the populated field in this example is actually phone_2__v where the value is entered when the user adds new phone fields to the profile. This leaves the phone_1__v field blank.
The user can verify this by running an Ad-Hoc Query on the record in question. The results appear in this example:
"phone_2__v": "+09 45678900"
While phone_1__v returns a null value:
The user adds new phone fields on the HCP or HCO profiles by clicking Add Phone. The user enters a value in only one of the fields and leaves the rest blank. Network populates the phone number in the corresponding phone field (which the value has been added to), based on the order of the fields.