Key success factors for managing emails in SharePoint are:
They can be configured to record in your existing metadata columns.
When a user saves an email to a private or public folder in Outlook they simply drag and drop from the InBox or Sent Items folder to the private or public folder – they are not prompted for any additional details. So when an organisation introduces SharePoint as the new way of managing emails it’s not surprising that a key success factor is that email saves should still be via drag and drop and that there should be no prompting for metadata.
In other words if you want to ensure user adoption when SharePoint replaces Outlook folders you need the recording of email attributes such as To, From, Subject, etc. to be fully automatic.
The MacroView user can do the save by dragging and dropping to a document library, document set or folder that is displayed in the MacroView pane located on the right side of the Outlook Mail window. In addition, MacroView is designed to automatically record the attributes of the email as metadata in the destination area without any prompting of the user.
This YouTube video shows MacroView DMF saving emails to Office 365 SharePoint Online. The experience is the same when saving to an on-Premises SharePoint Server, using MacroView DMF or MacroView Message.
MacroView DMF and MacroView Message achieve this zero prompting in two ways:
1) If the destination area in SharePoint contains multiple content types, MacroView will automatically select an Email content type (if it is available). The MacroView software can be configured to select a content type with a different name – e.g. Correspondence or Email Message. The main thing is that the MacroView user does not have to choose a content type.
2) The MacroView software will automatically record all the non-personal attributes of the email in corresponding metadata columns in the selected content type, if those corresponding metadata columns are available. The non-personal attributes include To, CC, BCC, From, Subject, Conversation Topic, Attachment Count, Importance, Sensitivity and Email Message ID.
By default, MacroView DMF and MacroView Message will look to record the To attribute of the email in a metadata column with the internal name mvTo; the From attribute in a metadata column with internal name mvFrom, etc. The MacroView software ships with a site content type (called Email) that contains metadata columns corresponding to all the non-personal attributes of Outlook emails. By including that Email site content type in your SharePoint document libraries you will see the automatic metadata recording happen as you save Outlook emails.
MacroView DMF and MacroView Message can be configured so that they record email attributes in metadata columns with different internal names. For example the To attributes in a metadata column called Mail_To; the From attribute in a metadata columns called Mail_From, etc. This is great news if you already have existing document libraries with metadata columns that are not those that MacroView uses by default. This configuration is at no additional cost – to arrange this configuration contact MacroView Services.
If the destination content type contains metadata columns that MacroView Message and MacroView DMF cannot record automatically, the user will be prompted to supply values for those columns. However as you design a SharePoint email store you should keep in mind that end-users regard zero-prompting as emails are saved as a major plus.
There are many other ways in which MacroView Message and MacroView DMF help to ensure user adoption when SharePoint Online or on-Premises replaces Outlook folders for managing emails. These include:
For more information about how MacroView Message and MacroView DMF facilitate the management of emails (and other files) in Office 365 SharePoint Online or in an on-premises SharePoint Server contact MacroView Services.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.