Purpose
The Email Mapping customisation automatically sets email properties to non-MacroView columns when an email is saved to SharePoint via MacroView DMS.
There are three ways to setup the Email Mapping customisation:
- User option in Office options
- A configuration file (XML) in your resource library specifying columns mappings
- The Email Mapping customisation (MSI) installed on the client machine
User option in Office options
MacroView DMS 8.9.1343 and later allows each field to be changed from the Map Fields button under Options > Office.
You can edit the main fields
Or alter the email property they are mapped to
Or rename fields
You can also add additional fields and set multiple fields to map to the same email property
Clicking Restore Defaults will remove additional changes and revert to the stock values
Configuration file in a Resource library
MacroView DMS 8.9.1343 and later supports deploying the email mapping file form your resource library. To do this you need to download and update the below configuration file.
Email Mapping Configuration File
The file must be named EmailFieldMapping.json.config
The file needs to be stored in the "Config" folder inside your resource library.
UI storage location vs Resource Library storage location
The email field mapping can either be configured through the DMS UI in which case, the configuration is automatically stored in a JSON file at the top-level of the store folder or alternatively using a resource library with a "EmailFieldMapping.json.config" file uploaded to the Config directory.
Email Mapping Customisation (legacy approach)
This approach is not required when using MacroView DMS 8.9.1343 or later. To use the Email Mapping customisation you must create a custom configuration file and save it to your resource library then install the separate Email; Mapping extension.
Setting up your configuration file
The email mapping customisation will allow DMF to record default email metadata to your specified columns when saving emails to SharePoint from Outlook. See the table below for the list of columns available for mapping:
Email attribute | Source | Destination | Column type |
Conversation Topic | mvConversationTopic | customColumn1 | Single line of text |
Subject | mvSubject | customColumn2 | Calculated |
To | mvTo | customColumn3 | Single line of text |
From | mvFrom | customColumn4 | Single line of text |
CC | mvCC | customColumn5 | Single line of text |
BCC | mvBCC | customColumn6 | Single line of text |
Sent on | mvSentOn | customColumn7 | Date and Time |
Received Time | mvReceivedTime | customColumn8 | Date and Time |
Importance | mvImportance | customColumn9 | Single line of text |
Attach Count | mvAttach_x0020_Count | customColumn10 | Single line of text |
Sensitivity | mvSensitivity | customColumn11 | Single line of text |
Message ID | mvMessageID | customColumn12 | Single line of text |
To map your custom columns:
- Extract, then open EmailMapping.xml from downloaded .zip file
- Replace the Destination fields with the internal column name(s) of your custom email columns only. The example below shows that the MacroView column mvConversationTopic column will be mapped to the column named customColumn1.
For more information on finding internal column names see this article: How to check column internal name for a SharePoint list (external link)
- Once you have finished mapping all columns, save the xml file and close it.
- Finally, save the EmailMapping.xml to your central configuration location (Root resource library location).
- For more information see: Setting a central configuration location.
<?xml version="1.0" encoding="utf-8"?>
<FieldMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Fields>
<Mapping>
<Source>mvConversationTopic</Source>
<Destination>customColumn1</Destination>
</Mapping>
<Mapping>
<Source>mvSubject</Source>
<Destination>customColumn2</Destination>
</Mapping>
<Mapping>
<Source>mvTo</Source>
<Destination>customColumn3</Destination>
</Mapping>
<Mapping>
<Source>mvFrom</Source>
<Destination>customColumn4</Destination>
</Mapping>
<Mapping>
<Source>mvCC</Source>
<Destination>customColumn5</Destination>
</Mapping>
<Mapping>
<Source>mvBCC</Source>
<Destination>customColumn6</Destination>
</Mapping>
<Mapping>
<Source>mvSentOn</Source>
<Destination>customColumn7</Destination>
</Mapping>
<Mapping>
<Source>mvReceivedTime</Source>
<Destination>customColumn8</Destination>
</Mapping>
<Mapping>
<Source>mvImportance</Source>
<Destination>customColumn9</Destination>
</Mapping>
<Mapping>
<Source>mvAttach_x0020_Count</Source>
<Destination>customColumn10</Destination>
</Mapping>
<Mapping>
<Source>mvSensitivity</Source>
<Destination>customColumn11</Destination>
</Mapping>
<Mapping>
<Source>mvMessageID</Source>
<Destination>customColumn12</Destination>
</Mapping>
</Fields>
</FieldMapping>
Download the Email Mapping extension
Close Microsoft Outlook, DMF Explorer (if applicable) and the MacroView DMF Local Service then download and run the Email Mapping installer that corresponds with your installation of MacroView DMF or MacroView Message.
Email Mapping customisation 1.0.4 for 64-bit Windows
Email Mapping customisation 1.0.4 for 32-bit Windows
Minimum requirements
- MacroView DMF or MacroView Message 8.5.1145 to 8.9.1300*
Email Mapping customisation 2.0.0 for 64-bit Windows
Email Mapping customisation 2.0.0 for 32-bit Windows
Minimum requirements
- MacroView DMF or MacroView Message 8.7.19 to 8.9.1300*
* Important: MacroView DMF/Message 8.9.1340 and later has built-in email mapping, and as such this separate download is no longer required.