Why is PidTagLastVerbExecuted described here not same as MS-OXOMSG? #662
Replies: 6 comments
-
@dotfurther Hi, I don't understand the question. Is there a bug in one of the topics in this docset? I'm not sure what you mean by "described here" because there is no link provided. Please provide a link to the topic and the steps to repro so I can troubleshoot. Thanks, lindalu |
Beta Was this translation helpful? Give feedback.
-
If I go to the MS link below, and press the "Edit" button, it takes me to this repository for the help. And my question is why the almost completely different PidTagLastVerbExecuted definitions between 2 Microsoft documents. One of them is wrong. |
Beta Was this translation helpful? Give feedback.
-
Pressing the "Edit" button at this MS link: And the definition HERE is not same as the [MS-OXOMSG] definition of PidTagLastVerbExecuted: |
Beta Was this translation helpful? Give feedback.
-
@dotfurther This link refers to exchange_server_protocols and this link refers to Outlook 2013 client and Outlook 2016 client. What are you trying to do? Are you working in EWS or Outlook? What version? You could also ask your question to the developer community on Stack Overflow. Here is what I found when I searched for PR_LAST_VERB_EXECUTED. |
Beta Was this translation helpful? Give feedback.
-
I am working with Outlook client and PST saved.msg files. The PidTagLastVerbExecuted in Outlook client saved files follows the [MS-OXOMSG] definition. PR_LAST_VERB_EXECUTED is just an alias for PidTagLastVerbExecuted per [MS-OXOPROPS]: The Exchange master property list and the definition given here in this help repository are for the same property with ID 0x1081. But their defined values do not match up. It is the same MAPI property. It should have same definition for possible property values. Why do you think the same MAPI property (0x1081) should have different property value definitions in different specifications? |
Beta Was this translation helpful? Give feedback.
-
I'm not sure why they're different, but there are many properties so maybe they BOTH are correct. The protocol documents have had many revisions over the years. I wouldn't know how to even begin to track down the answer, that's why I think StackOverflow developers might be able to help. Have you tried using a MAPI editor like MFCMapi or OutlookSpy? It will tell you if that property has been set or not (its an optional property set by the client). I also learned that PR_LAST_VERB_EXECUTED is only set on the messages in your mailbox. Are you using VBA? You could try a search for the DASL name 0x10810003, you should be able to access it using MailItem.PropertyAccessor.GetProperty. Also, Referencing Properties by Namesake topic might be helpful. |
Beta Was this translation helpful? Give feedback.
-
Completely different PidTagLastVerbExecuted values from [MS-OXOMSG] spec:
https://docs.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-oxomsg/87a8b6b8-59a4-4859-9dcd-8b0f36e3d729
Why is that?
Beta Was this translation helpful? Give feedback.
All reactions