Forum Discussion
Ethan Li
Microsoft
Microsoft[New!] Drag and drop conversations into groups
Good news! We're currently rolling out drag and drop for messages and conversations into groups in Outlook on the web first for First Release customers, then Standard release customers.
It's mu...
We really need some more features to make this useful. I can not get the "select 100 messages" and drag and drop to work. First off, when you try to select several messages using control+click, it doesn't work, you can only control+click a few at a time. Second, the drag and drop doesn't work for me for multiple messages, only one by one.
Now, that just explains how the current functionality doesn't work. For future functionality, we need the following:
1. Drag and drop in outlook
2. Drag and drop all messages, not just some (I have a public folder I would like to move all the contents from but currently there is no way to do this)
I would prefer that the e-mail (and following replies) conversation was not moved or copied to the group, but "made visible" to the group.
This would also make it possible to make emails associated with multiple groups.
The current architecture of groups appears to move e-mails to a group inbox, removing it from the persons inbox, adding info on the to/copy fields etc.
Currently Hiver for Gmail is architected in this way. All emails of a company resides in the employees mailboxes. Visibility BEYOND what is seen in the to/cc/bcc fields is set by the hiver database table that holds visibility permissions. Adding a tag to an e-mail makes it visible beyond what the visibility in to/cc/bcc controls.
Groups seem to handle visibility in to/cc/bcc fields, and thus copying emails into multiple "PST" storage files. I can only Imagine this also makes a lot of unneccesary data in the server. Also search appears to be complicated by this architecture.
This would also make it possible to make emails associated with multiple groups.
The current architecture of groups appears to move e-mails to a group inbox, removing it from the persons inbox, adding info on the to/copy fields etc.
Currently Hiver for Gmail is architected in this way. All emails of a company resides in the employees mailboxes. Visibility BEYOND what is seen in the to/cc/bcc fields is set by the hiver database table that holds visibility permissions. Adding a tag to an e-mail makes it visible beyond what the visibility in to/cc/bcc controls.
Groups seem to handle visibility in to/cc/bcc fields, and thus copying emails into multiple "PST" storage files. I can only Imagine this also makes a lot of unneccesary data in the server. Also search appears to be complicated by this architecture.
- "Set regarding" in Dynamics CRM somehow is more like this, but only supports one association.
- A problem with having "group" adresses in the to/cc/bcc fields is that people who replies to an e-mail might want to interfer by deleting that group e-mail adress to "control" whom recieves the email.