Get unpredictable values - ConversationIndex RRS feed

  • Question

  • Hello folks,

    As a rule, you can find my name answering questions here. But now I have to ask other community members or Microsoft representatives. 

    The ConversationIndex property of Outlook items returns a string value that indicates the relative position of the item within the conversation thread. Under the hood it is represented by the GUID with further timestamps. Each time a user replies to a message (send it), a new timestamp is added (the last five bytes). Here is what it should look like:







    But sometimes I see the following picture:








    Is there a bug somewhere? Does anybody know why I get unpredictable results?

    Sunday, February 16, 2014 6:58 PM

All replies

  • Hi Eugene,

    Thanks for your feedback. ConversationIndex is usually implemented using concatenated time stamp values. The picture your post will happen in some specific scenarios; for example, the user is removed from the “To” list in one email.

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, February 17, 2014 8:35 AM
  • Hi Jeffrey,

    I know how the index is constructed. You get the right results. In my initial message here I showed two separate conversations with entirely different results: the first conversation looks good (as yours), but the second conversation gives wrong values. Only guid remains untoched with some previous timestamps. I expected to get only the last 5 bytes added. Instead, I get the last five changed and new five bytes added. Note, I didn't change anything in emails in both cases. The timestamp should use the UTC time, but it looks like it doesn't.

    Could you please contact developers?

    Monday, February 17, 2014 9:28 AM
  • Hi Eugene

    Have you had any further success with this? 

    If not, I'm going to raise a ticket as I'm having similar issues



    Tuesday, June 17, 2014 2:36 PM
  • Hi Sam,

    I didn't do anything further because I work on another project now.

    Glad to know that I am not alone who sees such results. Feel free to contact me if you need my assistance in reproducing the issue.

    Please let me know your results. 

    Tuesday, June 17, 2014 3:22 PM