none
When multiple users open and edit same contact in public folder within minutes apart

    Question

  • While our custom public folder of contact data controlled by an add-in is now public to all 50 users, we are encountering an issue where more than 1 user may edit the same contact.  For example, one computer 1, a user may make a change to this one contact in let's say the business phone as a correction, then save and close.  About a few minutes later, another user on a different workstation may open the same contact and make a correction in the memo field but intriguingly the change from the first user involving the business phone was not reflected when 2nd user opened this contact, and when 2nd user saves change, then the reading pane indicates the following:

    "Conflict Message:  Conflicting edits were made to this item.  Open the item to resolve this conflict."

    Now I can't seem to rid this reading pane message even if I just open the item.

    Is there a particular setting I may be missing which should reflect live changes like these?  It seems the only other way to ensure changes were up to date on all workstations is to keep exiting and reopening outlook all the time, which I consider to be unacceptable.  

    Tuesday, February 26, 2013 5:03 PM

Answers

  • Outlook cannot see changes unless they are made through the Outlook UI or the Outlook Object Model.

    This is a known limitation, there is nothing you can do about that.

    As for the conflicts message, you should be able to use ContactItem.Conflicts collection. Oulook Object Model will not let you clear that collection, I don't know if deleting the PR_CONFLICT_ITEMS property  (0x10981102) using PropertyAccessor will work, but it is worth trying.


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.4 is now available!

    Tuesday, February 26, 2013 5:29 PM
  • It does, but the change is made from another machine, so even though Outlook (in theory) can catch the chnage notification, it will not refrefsh its cached data.

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.4 is now available!

    Tuesday, February 26, 2013 8:11 PM
  • These guys set a special named property on the item and then save the item. When the item is closed, the property is deleted and the item is saved again. The second instance then checks if the property is set before opening the item.

    It might probably make sense in some cases, but I would not do it - too error prone (what if the first instance of Outlook crashes and the property is never removed?) and each item changes every time it is opened, even if no changes are made by the user.


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.4 is now available!

    Wednesday, February 27, 2013 4:37 PM

All replies

  • Outlook cannot see changes unless they are made through the Outlook UI or the Outlook Object Model.

    This is a known limitation, there is nothing you can do about that.

    As for the conflicts message, you should be able to use ContactItem.Conflicts collection. Oulook Object Model will not let you clear that collection, I don't know if deleting the PR_CONFLICT_ITEMS property  (0x10981102) using PropertyAccessor will work, but it is worth trying.


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.4 is now available!

    Tuesday, February 26, 2013 5:29 PM
  • When referring to the Outlook UI or the Outlook Object Model, does that not include add-in installed form regions along with those defined as a separate class such as IPM.Contact.Rolodex?
    Tuesday, February 26, 2013 7:11 PM
  • It does, but the change is made from another machine, so even though Outlook (in theory) can catch the chnage notification, it will not refrefsh its cached data.

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.4 is now available!

    Tuesday, February 26, 2013 8:11 PM
  • I came across this following link but was wondering how easy or hard this is to incorporate to prevent conflict messages:  http://www.assistmyteam.net/KB/index.php?option=com_content&view=article&id=144:how-to-prevent-exchange-conflicts-from-happening-when-two-or-more-users-edits-the-same-case-item&catid=18:team-helpdesk-for-sharepoint-a-outlook&Itemid=31
    Wednesday, February 27, 2013 4:13 PM
  • These guys set a special named property on the item and then save the item. When the item is closed, the property is deleted and the item is saved again. The second instance then checks if the property is set before opening the item.

    It might probably make sense in some cases, but I would not do it - too error prone (what if the first instance of Outlook crashes and the property is never removed?) and each item changes every time it is opened, even if no changes are made by the user.


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.4 is now available!

    Wednesday, February 27, 2013 4:37 PM