Add a custom field to the Contact profile

Contact management in Xperience by Kentico is an essential tool of digital marketing for your customers. Each contact represents a visitor and contains information, such as personal details, their consents or activity.

In Xperience source code, the Contact class has a predefined set of fields to store customer information. But in many cases, your customer needs to track custom domain-specific data about visitors, e.g., their favorite coffee.

Overview

You can add custom properties to the contact class using the administration interface.

To expose the custom fields for editors and marketers, we recommend creating a custom UI page with a new UI form and displaying it on a new tab in the Contact profile.

This article will guide you step-by-step through the process.

Before you start

This guide requires the following:

• Familiarity with C#, .NET Core, Dependency injection, and the MVC pattern.
• A running instance of Xperience by Kentico, preferably 29.6.1 or higher.
  Some features covered in the Training guides may not work in older versions.

Add custom database columns to Contact

1. Open the Modules application and select the Contact management module.
2. On the Classes tab select the Contact class (code name OM.Contact).
3. Switch to the Database columns tab and add custom fields using the field editor. For our example, let’s add these three fields:
   1. TrainingGuidesContactMemberId
      • Data type: Text
      • Size: 200
   2. TrainingGuidesContactFavoriteCoffee
      • Data type: Text
      • Size: 200
   3. TrainingGuidesContactLastCommunicationDate
      • Data type: Date and time
   Make all the fields NOT required (uncheck the Required check box).

In your Xperience administration, your new fields will appear at the bottom of the list:

Define your UI form

1. Stay in the Contact class under the Contact management module.
2. Switch to the UI forms tab.
3. Click New UI form button and fill out:
   • UI form name: Training guides fields edit
   • Code name: TrainingGuidesFieldsEdit
   Leaving Pre-fill code name automatically checked will generate the same code name in this case.

4. Click Save to create your new UI form.
5. Switch to the Fields tab in the left menu.
6. Add a new UI field for each of your custom Contact fields:
   1. Click New field.
   2. Select a database column you want to map the field to. The available columns are sorted alphabetically.
   3. Fill out field settings as desired and hit Save.
   If you are following our example, add three fields - one for each of our new database columns.

Implement your new edit page

You now have a custom UI edit form, holding your custom contact fields. You can display the form to editors by passing its code name to a new edit page in your code.

1. In your source code, navigate to your administration customization project (e.g. TrainingGuides.Admin).

2. In Pages folder, create a new class file, ContactCustomFieldsEditPage.cs.

3. Implement your custom edit UI page:

   C#

   ContactCustomFieldsEditPage.cs

   Copy

   
   using CMS.ContactManagement;
   using Kentico.Xperience.Admin.Base;
   using Kentico.Xperience.Admin.Base.Forms;
   using Kentico.Xperience.Admin.DigitalMarketing.UIPages;
   using TrainingGuides.Admin.Pages;
   
   // Register the page as using EDIT template, under "Custom fields" name.
   // parentType and order attributes determine it's position in the UI.
   // See more details in the next section, under the code sample.
   [assembly: UIPage(
       parentType: typeof(ContactEditSection),
       slug: "training-guides-fields-edit",
       uiPageType: typeof(ContactCustomFieldsEditPage),
       name: "Custom fields",
       templateName: TemplateNames.EDIT,
       order: 150)]
   
   namespace TrainingGuides.Admin.Pages;
   
   // All edit pages inherit from the InfoEditPage<TInfo> base class.
   // Substitute TInfo with the ContactInfo class - to tell Xperience this is to edit the Contact object type.
   public class ContactCustomFieldsEditPage : InfoEditPage<ContactInfo>
   {
       // Holds the ID of the edited contact.
       // Needs to be decorated with the PageParameter attribute to propagate
       // contact ID from the request path to the configuration of the page.
       [PageParameter(typeof(IntPageModelBinder))]
       public override int ObjectId { get; set; }
   
       // Mandatory constructor providing required services via dependency injection.
       public ContactCustomFieldsEditPage(
           IFormComponentMapper formComponentMapper,
           IFormDataBinder formDataBinder) : base(formComponentMapper, formDataBinder)
       { }
   
       public override Task ConfigurePage()
       {
           // Assign your 'TrainingGuidesFieldsEdit' UI form code name to the page. The assignment is case-insensitive.
           PageConfiguration.UIFormName = "trainingguidesfieldsedit";
           return base.ConfigurePage();
       }
   }
   

Specify the page tab position in the UI tree

...
[assembly: UIPage(
        parentType: typeof(ContactEditSection),
        slug: "training-guides-fields-edit",
        uiPageType: typeof(ContactCustomFieldsEditPage),
        name: "Custom fields",
        templateName: TemplateNames.EDIT,
        order: 150)]
...

We’ve decided to render our Custom fields page tab between the Overview and Activities tabs in the Contact profile:

When adding a page to an existing structure, you can achieve this by setting parentType to an existing application page. In this case, the ContactEditSection type.

If you register a UI page without specifying order, Xperience will place the new page tab last.

By default, the order of existing pages is set in increments of 100. In our example, we set order: 150 to place the Custom fields page tab between the Overview (100) and Activities (200) tabs.

Now, when you build your solution and open a profile of any contact in your Xperience administration, you should be able to see your new UI form in a custom tab, as illustrated in this video:

Additionally, if you navigate to System → UI tree, you should be able to see your page in the UI tree structure:

Customize the form fields

In some cases, you will need to show values that are based on contact data but not directly tied to a database column. Maybe the editors don’t care about the contact Member Id you created earlier. Instead they only need to know whether the contact is a member or not.

Let’s modify the form to replace the editable Member Id with a readonly flag Is a member: Yes/No.

1. Navigate to your Training guides fields edit form in your Xperience administration (Modules → Contact management → Classes → Contact management → Contact → UI Forms → Training guides fields edit).

2. In the Fields tab, remove the Member Id field.

3. Add a new field. In the Database column select, pick New field without database column.

4. Fill out the following:

   • Field name: TrainingGuidesContactIsMember
   • Data type: Text
   • Field caption: Is a member
   • Form component: Text with label (as the value is supposed to be readonly)

5. Save and optionally drag and drop the new field to your desired position (e.g. the top).

6. Open your ContactCustomFieldsEditPage.cs file.

7. Define constants to hold the names of the custom fields.

   C#

   ContactCustomFieldsEditPage.cs

   Copy

   
   ...
   private const string CONTACT_IS_MEMBER_FIELD_NAME = "TrainingGuidesContactIsMember";
   private const string CONTACT_MEMBER_ID_FIELD_NAME = "TrainingGuidesContactMemberId";
   ...
   

8. Add a GetFormItems method override:

   C#

   ContactCustomFieldsEditPage.cs

   Copy

   
   ...
   protected override async Task<ICollection<IFormItem>> GetFormItems()
   {
       // Retrieve form items.
       var items = await base.GetFormItems();
       // Return a method call that modified the form items. Implemented in the next step.
       return SetContactIsMember(items);
   }
   ...
   

9. Implement SetContactIsMember(items) method:

   C#

   ContactCustomFieldsEditPage.cs

   Copy

   
   ...
   /// <summary>
   /// Sets the value of the "Is a member" field based on the value of the "Member ID" field.
   /// </summary>
   /// <param name="items">Collection of form items</param>
   /// <returns>The updated collection of items</returns>
   private ICollection<IFormItem> SetContactIsMember(ICollection<IFormItem> items)
   {
       // Retrieve the 'Is a member' field.
       var contactIsMemberField = items.OfType<IFormComponent>()
           .FirstOrDefault(i => i.Name == CONTACT_IS_MEMBER_FIELD_NAME) as TextWithLabelComponent;
       // Calculate the string value of 'Is a member' field, based on the 'Member Id' value.
       // GetContactMemberId() implemented in the next step.
       string contactIsMember = string.IsNullOrEmpty(GetContactMemberId())
           ? "No"
           : "Yes";
   
       // Set the new value to the 'Is a member' field.
       contactIsMemberField?.SetValue(contactIsMember);
   
       return items;
   }
   ...
   

10. Implement GetContactMemberId() to retrieve the value of TrainingGuidesContactMemberId field:

    C#

    ContactCustomFieldsEditPage.cs

    Copy

    
    ...
    // Inject contactInfoProvider.
    private readonly IInfoProvider<ContactInfo> contactInfoProvider;
    
    public ContactCustomFieldsEditPage(
        IFormComponentMapper formComponentMapper,
        IFormDataBinder formDataBinder,
        IInfoProvider<ContactInfo> contactInfoProvider)
                : base(formComponentMapper, formDataBinder)
    {
        this.contactInfoProvider = contactInfoProvider;
    }
    
    ...
    // Use contactInfoProvider to retrieve the current Contact
    // and get the value of the TrainingGuidesContactMemberId field.
    private string? GetContactMemberId() =>
        contactInfoProvider.Get()
            .WhereEquals(nameof(ContactInfo.ContactID), ObjectId)
            .FirstOrDefault()
            ?.GetValue(CONTACT_MEMBER_ID_FIELD_NAME) as string;
    ...
    

11. Build your solution. If you followed along, your page in Contact profile should now look similar to this:

    

Enable custom fields in Contact groups

Contact groups allow to editors organize contacts by defining custom conditions.

Since the 29.1.0 Xperience by Kentico refresh, the editor can set up a new condition, ‘Contact has value in field’.

Your contact fields are not yet available for the editor to utilize in this condition. To expose them, you need to add your custom fields to the Contact edit form.

1. Navigate to the Contact edit form in your Xperience administration (Modules → Contact management → Classes → Contact management → Contact → UI Forms → Contact edit).

2. Add your fields one by one.

   When assigning a Database column, the available fields are ordered alphabetically.

   The Field caption is what the editors will see in the Contact groups application as a field identifier. The other settings don’t affect the Contact groups conditions.

What’s next

You now have the tools to add custom fields to Contact and expose them to the editor. You also know how to create a custom UI page displaying a custom UI form.

In this guide, we created a page using the edit UI page template. On this page, you can read more about other available templates, their methods, and usage.

If you are interested in learning how to create a custom class in Xperience rather than just extending system objects, take a look at our next guide series. Over the course of four guides, the series shows how to build a custom “settings” module.