Unique Message ID and Conversation ID

asked on May 4, 2016

Within the "Tools>Options" menu in the Laserfiche Client, I have mapped the Outlook elements "Unique Message ID" and "Conversation ID" to metadata fields with the same name. All other Outlook elements have been mapped to same named metadata fields as well. I see that similar options appear in the Admin Console within the "Repository Options>Default Outlook Import Options" menu, but there's no Unique Message ID or Conversation ID elements to map.

Upon import using the Laserfiche Ribbon in Outlook, all the fields are populated with the appropriate Outlook elements except for Unique Message ID and Conversation ID.

Are there additional options that I'm missing to get these ID's to be filled in upon import?

2016-05-04_1626.png (68.9 KB)

| Download

0 0

replied on May 4, 2016

Hey Rob,

I'll look into the inconsistency there. In the meantime, I'm curious what you're using those tokens for - are you tying them into some other process?

1 0

View 3 previous replies

replied on May 5, 2016

Thank you very much, Pava!

I'm hoping that I can use the Conversation ID to recognize when a new email is imported from a conversation that already has been imported in the repository. I understand that if the subject remains the same for every message in the conversation, then Laserfiche can use version control to add versions to the same entry. In many cases though, we'll have an email thread where some people reply and others forward, and we'll end up having three different entries stored side by side, "Message Subject", "RE: Message Subject", and "FW: Message Subject". More applications of this data may arise in the future.

0 0

replied on May 11, 2016

Hi Rob, this is targeted to be fixed in an upcoming version (ref # 144034). Until then, you can configure the outlook settings manually by setting attributes on the Everyone group. Add an attribute [Settings]MsgImp_Field_fieldname (replace fieldname with the actual name of the field). Set it to 11 for the conversation id, and 12 for the message id. The desktop client will recognize this and populate the fields during import.

1 0

replied on May 11, 2016

Hey Rob! Thanks for the message, but it doesn't look like that fixed it. I made the following changes and restarted Client and Outlook and tried another import to find the fields still blank.

Field_List.png (13.66 KB)

| Download

Attributes.png (7.71 KB)

| Download

0 0

replied on May 11, 2016

Are those attributes set on your user? If so, that would override what is set on the Everyone group.

0 0

replied on May 11, 2016

They were set in the user attributes until just now. I believe that was a result of the right screenshot in the original post, where the IDs were set in the Client's options menu.

I removed those settings in the client options, manually removed the attributes from the user's account, restarted Client and Outlook again, reimported, but still no luck.

0 0

replied on May 11, 2016

My mistake, I thought you were importing through the desktop client. We will look into getting the Outlook integration to support these properties.

0 0

Question

Question

Unique Message ID and Conversation ID

Replies

Sign in to reply to this post.