3.1.5.1 Modifying a Contact Name Property

Contact Name properties MUST be modified at the same time to preserve their relationship. The following table specifies the properties that SHOULD be updated when another property is changed (according to the definition of each property in section 2.2.1 of this specification). More than one condition can be met at the same time. Not all properties will need to be updated every time. Clients use the grouping of specifications in section 2.2.1 and section 2.2.1.2.8 to determine whether an update is required.

Changed property

Conditions

Properties that SHOULD be updated

PidTagGeneration (section 2.2.1.1.2)

None.

PidTagDisplayName (section 2.2.1.1.8), PidTagNormalizedSubject (section 2.2.1.11.1)

PidTagGeneration or PidTagSurname (section 2.2.1.1.4) or PidTagMiddleName (section 2.2.1.1.5) or PidTagGivenName (section 2.2.1.1.6) or PidTagDisplayName or PidTagCompanyName (section 2.2.1.6.2)

Value of the PidLidFileUnderId property (section 2.2.1.1.12) is not 0x00000000 or 0xFFFFFFFF.

PidLidFileUnder (section 2.2.1.1.11)

PidTagDisplayNamePrefix (section 2.2.1.1.3)

None.

PidTagDisplayName

PidTagSurname (section 2.2.1.1.4) or PidTagMiddleName or PidTagGivenName

None.

PidTagDisplayName, PidTagNormalizedSubject, PidTagInitials (section 2.2.1.1.7)

PidTagDisplayName

None.

PidTagDisplayNamePrefix, PidTagGivenName, PidTagMiddleName, PidTagSurname, PidTagNormalizedSubject, PidTagGeneration

The client SHOULD also update the PidLidFax1EmailAddress (section 2.2.1.2.8), PidLidFax2EmailAddress (section 2.2.1.2.8), or PidLidFax3EmailAddress (section 2.2.1.2.8) properties as needed to reflect any updates to the Contact Name properties if the contact has a Primary Fax, Business Fax, or Home Fax address, respectively.