You are viewing limited content. For full access, please sign in.

Question

Question

LF10 Outlook Integration - drag-and-drop behavior in Outlook changed

asked on February 9, 2016

Our users are reporting a new (and undesirable) behavior with the LF10 Outlook plugin. When someone drags an email from one folder to another in Outlook, the message list focus is being set to the top of the list. So for example, say you're 100 messages down in your email list and you highlight a message and drag it to another folder in Outlook. As soon as you drop the message in the folder you are repositioned to the first message at the top of the message list. If you were in the process of filing a bunch of messages to different folders, this causes a lot of extra scrolling/aggravation. Uninstall the Laserfiche plugin and the Outlook behavior returns to normal - you are left positioned where you were when you started the drag-and-drop. We have a lot of users that organize mail into folders using drag-and-drop, so the change, while minor, isn't minor to them.

Any chance we can get the standard Outlook behavior back please?

1 0

Replies

replied on February 10, 2016

Hi Geoffrey,

I'm not seeing this behavior (I'm using Office 2013). What version of Outlook are your users using? It's certainly not a deliberate change - it might be a side effect of supporting drag-drop directly into Web Access, and we can take a look into it if we can reproduce it. 

0 0
replied on February 10, 2016

We're using Office/Outlook 2010

0 0
replied on February 10, 2016 Show version history

CORRECTION: We were experiencing this in our organization also using Outlook 2010.  Upgrading to Office 2016 fixed the issue.

0 0
replied on February 10, 2016

Alright, thanks. We'll take a look and see if we can reproduce it on Office 2010. Glad to hear that upgrading the version of Office works, although obviously that's not an answer in all cases. 

0 0
replied on February 11, 2016

Is there any update yet? Have you been able to reproduce the issue? 

0 0
replied on February 11, 2016

I was talking more long-term. If you need an immediate response, please open a support case. 

0 0
replied on February 13, 2016

We confirmed the issue only occurs on Outlook 2010. This issue should be fixed in next release.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.