Configure Custom Email View and Email Header Mapping in New harmon.ie
When users save emails to Microsoft 365, New harmon.ie can automatically create an Email view and map email headers to SharePoint columns.
This article explains how you can customize the mapping of email headers to SharePoint columns, in case your Microsoft 365 environment already has pre-built email views and columns.
If custom email views and email header mapping are configured in harmon.ie Classic, you’d have to configure them in New harmon.ie as explained below.
Configuring custom email header mapping
Steps:
- Prerequisite: Set up the configuration for New harmon.ie.
- Download Provisioning.zip and extract it to a local folder.
- Edit the extracted Provisioning.json file:
The EmailHeaderMapping section includes key-value pairs that set custom email header mapping in harmon.ie:- Each key is an email header or column display name.
- The value is an array of static column names as defined in your organization. If different libraries have different static column names for saving email headers, define all of them in a comma-separated list.
Example: "To": ["EmailTo1", "To1"]
harmon.ie’s initial mapping includes a list of static column names as described in the table below.
Update the Provisioning.json file only if your configuration includes other column names.
SharePoint columns used for email header mapping:
Key: Column Display Name | Value: Static Column Names | Type | Description |
---|---|---|---|
Attachments | [“hrmV2HasAttachments”, “hrmHasAttachments”, “hrmAttachments”, “HasAttachments”, “Attachments”, “Attachment”, “MailAttachments”, “WithAttachments”] | Single line of text | Indicates if the email message contains attachments. |
Categories | [“hrmV2Categories”, “hrmCategories”, “Categories”] | Multiple lines of text | Message categories. COMING SOON. |
CC | [“hrmV2CC”, “hrmV2Cc”, “hrmCc”, “hrmCcOWSMTXT”, “EmailCc”, “Cc”, “MailCc”] | Single line of text | The identity of the secondary recipients of the message. |
Conversation Index | [“hrmV2ConversationIndex”, “hrmConversationIndex”, “Conversation-Index”, “ConversationIndex”] | Single line of text | A unique identifier for the conversation. |
Conversation Topic | [“hrmV2ConversationTopic”, “hrmConversationTopic”, “Conversation-Topic”, “ConversationTopic”] | Single line of text | The original subject of the email thread (without “FW:”, “RE:”). This column facilitates creating a SharePoint view to show threaded emails. |
Date | [“hrmV2Date”, “hrmDate”, “EmailDate”, “Date”, “MailDate”] | Date and Time | The date and time when the message was sent. |
From | [“hrmV2From”, “hrmFrom”, “EmailFrom”, “EMailSender”, “From”, “From1”, “MailFrom”, “Sender”] | Single line of text | The address of the message sender. |
MessageID | [“hrmV2MessageID”, “hrmMessageID”, “MessageID”] | Single line of text | A unique identifier for the message. |
Received | [“hrmV2Received”, “hrmV2Recieved”, “hrmReceived”, “EmailReceived”, “Received”] | Date and Time | The date and time when a message is received. |
Subject | [“hrmV2Subject”, “hrmSubject”, “EmailSubject”, “Subject”, “MailSubject”] | Single line of text | The subject of the message. |
To | [“hrmV2To”, “hrmTo”, “EmailTo”, “To”, “MailTo”] | Single line of text | The identity of the primary recipients of the message. |
Additional key in the Provisioning.json file
Besides the email header columns, you may also need to define the ContentTypes key if you’ve used a different name to the email content type:
KEY | VALUE | DESCRIPTION |
---|---|---|
ContentTypes | [“EMail”, “E-Mail”] | Email content types that should be used when uploading an email. |