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

All about SharePoint List View Styles

Sometimes, there are out of the box features which we tend to ignore and later when we do apply, we are more than happy about the feature which is readily available in SharePoint. One such feature is List View Style. I never thought I would write a post on this. However, whenever I spoke about this with users, people were excited to see the result. That prompted me to write this post. Instead of getting into only theory part, I will basically take use cases where these styles can be applied and also touch up on on some minor limitations with certain style. When you are creating/modifying a List view, you will get an option to select View Style. As shown below, there are 8 options available and Default is always set if you ignore this style. List of View Styles I will take typical Contact List and Announcement List to explian about these styles. Let us go one by one. Default: This view, as name suggest, is the default style in a view. This is one of the widely seen style ...
1 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

How to get SharePoint List or Library GUID via REST

Sometimes, you would need List or Library GUID to use that in some operation. In such cases, how do you get hold of GUID using REST API? There is a straight-forward end point which you can use: /_api/web/lists/getByTitle('ListTitle')/Id This will return the GUID of a List or Library. There is also another approach. However this approach works only if a List or Library contains at least one item. /_api/web/lists/getByTitle('ListTitle')/items This is a familiar end point which we use to fetch items of a List or Library. To get the GUID from the response, you would do: var listIDTemp = response.data.d.results[0].__metadata.id; var listID = listIDTemp.substring(listIDTemp.lastIndexOf("guid") + 5).split('\'')[0]; As you can see, we are doing string operations to fetch GUID from metadata.id. This contains information only if the response has at least one item.
Post a Comment
Read more