Skip to main content

Drag and Drop Outlook Email to SharePoint Library

Recently, I got a question on drag and drop possibility from Outlook to SharePoint Library. This question prompted me to write this post to share details on the topic.

Question: After I integrate SharePoint Document Library with Microsoft Outlook, can I drag email from Outlook to Document Library folder within Outlook?

Unfortunately the answer is No. For the benefit of the people who are new to the integration, let me explain more on this topic. Suppose you have created a document library in a SharePoint portal. On Library tab, when you click on "Connect to Outlook", a folder gets created in Outlook and data is pulled from Library to your Outlook. Any changes to the contents in the library will get synchronized with Outlook.

With this feature enabled, it is obvious for the user to think that if email is dragged and dropped from Inbox to the Library, it should get saved in the SharePoint. But, it does not work! This feature is not available. However, there is a work-around to achieve something similar. In SharePoint site, navigate to the library, click on Library tab, click on "Open with Explorer". Wait for some time till Windows Explorer is open. Now, you can drag email and drop it to Windows Explorer window. This will basically store the email in .msg format in library. Any attachment within the mail will also be saved within the .msg file. The subject of the mail becomes the file name in the library.

If you do similar Outlook integration with Discussion Forum, Outlook allows you to drag and drop mail to Discussion Forum folder within Outlook. The subject of the mail becomes subject of the discussion and body of the mail becomes body. Any attachment in the mail is stored as an attachment to the discussion thread.

There are third-party components which addresses what is not possible in SharePoint. Here is the list. Note that, this list is provided only for information. You may have to research on the feasibility and take your own decision on going for it.

MacroView: http://www.macroview.com.au/Products/Pages/Message.aspx

OnePlaceMail: http://www.scinaptic.com/oneplacemail.html
Labels:

Comments

  1. AnonymousOctober 1, 2012 at 3:44 PM

    Try this : http://out2share.codeplex.com/documentation

    ReplyDelete
  2. SureshOctober 3, 2012 at 9:09 AM

    Thanks Anonymous!

    ReplyDelete
  3. UnknownFebruary 17, 2014 at 6:38 AM

    Great article.

    For drag and drop of emails from Outlook to SharePoint we are using Outlook SharePoint Integration tool, called PageLight. PageLight also offers Drag and drop Outlook Email to SharePoint functionality

    ReplyDelete
  4. DimitriMarch 2, 2016 at 3:41 AM

    We started off with MacroView Message and then upgraded to their DMF product for Office 365 - details can be found @ macroview365.com

    ReplyDelete

Post a Comment

Popular posts from this blog

Document ID Service - New Feature in SharePoint

When I explored this new feature of SharePoint in Online (this feature is available in SharePoint 2013 also), I found it interesting because it solved one of the common problems people faced in SharePoint. I will first explain about this feature and I'll cover the problem and the solution in another post. This feature allows Site Collection Admin assign a unique ID to every document in the site collection out of the box. If you recall, there was no out of the box way to assign a unique number to the documents across libraries in a site collection. Yes ID column is unique but only within a library. Document ID column contains a number which is unique across libraries. To start with, let's have a look at a typical document library. This is a familiar view for SP guys. By default, you don't get Document ID column in a library. All Items View To get Document ID column, you need to activate a site collection feature "Document ID Service" as shown below. S...
Post a Comment
Read more

How to update Person field with multiple values using REST API

Person or Group field in SharePoint is similar to a Lookup field. When you are updating this field using REST API, you need to append "Id" to the name of the column in the body construct. For example, the body construct looks like this: data: { "__metadata": { "type": "SP.Data. ListName ListItem" }, "Title": "First Item", " PeopleField Id": "4" }; The highlighted portions should be replaced by the actual List Name and Column Name. In the above example, the REST call is updating a List item with Title and People columns. How to get the value for user ID ("4" in the above example) needs a separate explanation and that will be my next post! The above example works fine if Person field is configured to accept only one value. If we change the Person field to accept multiple values, how do we pass more than one value in the REST call? Since we normally separate user names with semicolon in peop...
12 comments
Read more

Restrict Future or Past Date in List

Many a times you will come across a requirement wherein you need to restrict user from entering future or past date in a List or Document Library Date column. Developers are inclined towards writing either event handler or javascript to achieve this. But, hold on! You can achieve this without writing a single line of code. I have a list which stores Employee details like Employee Number, Name and Date of Joining. Here I need to enure that Date of Joining will not accept future date. Navigate to List Settings -> Validation Settings. Here you can enter the formula to restrict future date as shown below. If you change the logical operator, it will restrict past date. Also, you can put message which will be displayed to user. Now, when you try to enter future date and try Save, you will see the validation message. So, next time you have similar requirement, you know where to try first before jumping into coding!
14 comments
Read more