ContactList in Series 40

ContactList provides access to the Phonebook on-device database.

The fields of a phonebook entry must be mapped to PIM API standard fields whenever possible. The following table defines a mapping between native fields and PIM API fields for contact lists in the device memory.

In Series 40 implementations where the underlying native phonebook only has a single name field, it must be mapped to the Contact.FORMATTED_NAME field.

**Table 37:** The supported `Contact` fields and their attribute combinations
PIM API Field	PIM API Attributes	Corresponding Phonebook Field
`Contact.FORMATTED_NAME`*	`PIMItem.ATTR_NONE`	Name
`Contact.NAME`	`PIMItem.ATTR_NONE`	Name
`Contact.NICKNAME`	`PIMItem.ATTR_NONE`	Nick name
`Contact.ORG`	`PIMItem.ATTR_NONE`	Company
`Contact.TITLE`	`PIMItem.ATTR_NONE`	Job title
`Contact.BIRTHDAY`	`PIMItem.ATTR_NONE`	Birthday
`Contact.TEL`	`PIMItem.ATTR_NONE`	General
`Contact.TEL`	`Contact.ATTR_MOBILE`	Mobile
`Contact.TEL`	`Contact.ATTR_HOME`	Home
`Contact.TEL`	`Contact.ATTR_WORK`	Office
`Contact.TEL`	`Contact.ATTR_FAX`	Fax
`Contact.TEL`	`Contact.ATTR_FAX`	Fax
`Contact.TEL`	`Contact.ATTR_PAGER`	Pager
`Contact.TEL`	`Contact.ATTR_AUTO`	Car phone

The Series 40 implementation supports the following extended attribute:

Extended Attribute	Numeric attribute ID	Note
`ATTR_VIDEO_CALL`	0x1000000	`Contact.TEL` field video call attribute

The supported Contact.NAME string array elements are as follows:

Contact.NAME Element	Corresponding Phonebook Field
`Contact.NAME_FAMILY`	Last name
`Contact.NAME_GIVEN`	First name