First - I was not able to activate the edit function on the prior entry. I have the field "Phone" coded as NOT a Primary Field. After the update, it became a Primary Field again. FWIW - I've reported this issue repeatedly for several years. I didn't keep a record as it is an easy fix.
John Purdy ACT! Premium V. 18 Lenovo X220, 16GB, & Office 365, 32bit, 256GB SSD
We are aware of this. It is actually the current expected behaviour. Any system fields will have their default primary status restored as part of the schema update script. I'm not sure on the technical limitations of why this happens. I would suggest posting any feedback or suggestions you have for this process as a feature request in the Share Your Ideas board.
