Managing custom fields
A custom field is a user-defined field that stores information not otherwise provided in a contact profile. Custom fields display in tabs for contacts on the Contacts workspace.
You can add text, number, currency, convertible currency, date, and relationship custom fields. For example, you can add a custom date field that only accepts date values. Relationship custom fields only accept other contacts as values.
A custom field group enables you to group related custom fields together. A custom field group defines the following in NexJ CRM :
- The types of contacts that you can add the custom field to. For example, a custom field group can make a custom field available to only company contacts.
- The tab name that displays on a contact's profile on the Contacts workspace. For example, the custom fields in the Profile group display in the Profile tab in NexJ CRM .
A custom field can belong to only one group. By default, the Profile and Private custom field groups display on the Contacts workspace.
System administrators, business administrators, and users can use and manage custom fields in the following ways:
System administrators
In NexJ Admin Console, system administrators can create, modify, and delete custom fields and custom field groups.
Business administrators
On the Customize workspace, business administrators can create and delete custom fields, modify custom fields properties and contact types, and manage the order of custom fields.
Users
On the Contacts workspace, users can add and remove custom fields for individual contacts, modify custom field values, and add custom fields to the system. Users can also click the Options button and select an option to sort the custom fields by name or priority.
NexJ recommends that a business administration group manages custom field types.
Best practices for creating custom fields
Typically, a business administration group manages custom field types. This group usually has responsibility for:
- Collecting requests for new custom field types from users or teams
- Configuring new custom fields or leveraging existing custom fields
- Providing recommendations for use of existing custom fields
Best practices for using custom fields
Custom field data is useful because it becomes available for filtering, searching, and reporting as soon as it is added to the system.
Consider using custom fields to:
- Store optional contact data used by a limited number of contacts in the system
- Store contact-level information, for example, interests, demographics, and financial information
- Track relationships
Avoid using custom fields to:
- Store business-critical contact data that:
- Is frequently used for the majority of contacts in the system
- Is used by NexJ CRM business logic or that is integrated with other functionality in NexJ CRM, for example, Service Level Management (SLM) functionality
- Track aggregate account-level information, such as products and services, or restrictions. Custom fields do not aggregate at the household-level.
Some examples of custom fields include:
- Referral Source
- Favorite Sports Team
- Lawyer
Adding custom fields to contacts
You can add an existing custom field to a contact and specify a value for the field.
To add a custom field to a contact:
Modifying custom field values for contacts
You can modify values for custom fields that you have added to a contact.
To modify a custom field value for a contact:
Removing custom fields from contacts
Remove a custom field from a contact's record when you no longer need to track the information in the field.
To remove a custom field from a contact:
Opening a contact's profile from a custom field
Custom fields can accept other contacts as values. You can open the profile for a contact from a custom field that contains the contact as a value.
To open the profile for a contact from a custom field:
Adding custom fields to the system
If you have the appropriate permissions, you can create a custom field to store information that is not represented by existing custom fields. Otherwise, contact the business administration group or administrator who manages custom field types.
To add a custom field to the system:
In the Visibility field, define view security for the custom field. Select Public to make the custom field visible to all users, or select a user or group to restrict visibility to that user or group.
You cannot modify view security levels for the custom field after it has been created. If you want to restrict view access to this custom field, you must set it now. The default view setting is Public.
- In the Group field, select a custom field group to define the custom field tab in which the custom field is available.
In the Contact Types tab, add or remove contact types from the list on the right, which is the list of contact types in which the custom field is available.
By default, all contact types that are available to the custom field are selected.
Modifying custom fields in the system
If you have the appropriate permissions, you can modify properties for a custom field. Otherwise, contact the business administration group or administrator who manages custom field types. Changes made to a custom field also apply to all existing custom fields used by contacts.
To modify a custom field: