Converting HexEntryID of AppointmentItem returns EwsId which is not equal UniqueId of Appointment object











up vote
0
down vote

favorite












The case is:




  1. I am creating an Appointment object with EWS. Then save it and get property Id (ItemId type). The value is:



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAZkhghCeo1Q6ZG9jEcqo8CBwAYQQne/T3URoAICyAlQqoaAAAAAAENAAAYQQne/T3URoAICyAlQqoaAAAoUZCDAAA=





  1. From outlook add-in I'm getting AppointmnetItem object which has EntryId



0000000024A788DE4C8B164294726448FAD7032607005CFD2D234BED54439BEB222BA0522758000000EB36CF00003B52743257E27A4FA6AA876380A189520000D4ABD6530000





  1. I'm converting EntryId with EWS to EwsId format. This action returns



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAkp4jeTIsWQpRyZEj61wMmBwBc/S0jS+1UQ5vrIiugUidYAAAA6zbPAAA7UnQyV+J6T6aqh2OAoYlSAADUq9ZTAAA=




Why EwsId's are different?
(Note: EWS can't bind appointment object by EwsId from point 3)










share|improve this question
























  • What is the error when you try to use the id from #3?
    – Dmitry Streblechenko
    Nov 19 at 17:05










  • The error is "The specified object was not found in the store., The store ID provided isn't an ID of an item."
    – ip.Nightly
    Nov 20 at 4:06















up vote
0
down vote

favorite












The case is:




  1. I am creating an Appointment object with EWS. Then save it and get property Id (ItemId type). The value is:



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAZkhghCeo1Q6ZG9jEcqo8CBwAYQQne/T3URoAICyAlQqoaAAAAAAENAAAYQQne/T3URoAICyAlQqoaAAAoUZCDAAA=





  1. From outlook add-in I'm getting AppointmnetItem object which has EntryId



0000000024A788DE4C8B164294726448FAD7032607005CFD2D234BED54439BEB222BA0522758000000EB36CF00003B52743257E27A4FA6AA876380A189520000D4ABD6530000





  1. I'm converting EntryId with EWS to EwsId format. This action returns



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAkp4jeTIsWQpRyZEj61wMmBwBc/S0jS+1UQ5vrIiugUidYAAAA6zbPAAA7UnQyV+J6T6aqh2OAoYlSAADUq9ZTAAA=




Why EwsId's are different?
(Note: EWS can't bind appointment object by EwsId from point 3)










share|improve this question
























  • What is the error when you try to use the id from #3?
    – Dmitry Streblechenko
    Nov 19 at 17:05










  • The error is "The specified object was not found in the store., The store ID provided isn't an ID of an item."
    – ip.Nightly
    Nov 20 at 4:06













up vote
0
down vote

favorite









up vote
0
down vote

favorite











The case is:




  1. I am creating an Appointment object with EWS. Then save it and get property Id (ItemId type). The value is:



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAZkhghCeo1Q6ZG9jEcqo8CBwAYQQne/T3URoAICyAlQqoaAAAAAAENAAAYQQne/T3URoAICyAlQqoaAAAoUZCDAAA=





  1. From outlook add-in I'm getting AppointmnetItem object which has EntryId



0000000024A788DE4C8B164294726448FAD7032607005CFD2D234BED54439BEB222BA0522758000000EB36CF00003B52743257E27A4FA6AA876380A189520000D4ABD6530000





  1. I'm converting EntryId with EWS to EwsId format. This action returns



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAkp4jeTIsWQpRyZEj61wMmBwBc/S0jS+1UQ5vrIiugUidYAAAA6zbPAAA7UnQyV+J6T6aqh2OAoYlSAADUq9ZTAAA=




Why EwsId's are different?
(Note: EWS can't bind appointment object by EwsId from point 3)










share|improve this question















The case is:




  1. I am creating an Appointment object with EWS. Then save it and get property Id (ItemId type). The value is:



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAZkhghCeo1Q6ZG9jEcqo8CBwAYQQne/T3URoAICyAlQqoaAAAAAAENAAAYQQne/T3URoAICyAlQqoaAAAoUZCDAAA=





  1. From outlook add-in I'm getting AppointmnetItem object which has EntryId



0000000024A788DE4C8B164294726448FAD7032607005CFD2D234BED54439BEB222BA0522758000000EB36CF00003B52743257E27A4FA6AA876380A189520000D4ABD6530000





  1. I'm converting EntryId with EWS to EwsId format. This action returns



AAMkAGFmMmI3Y2ZkLWRlNjktNDgyNi1iOTYyLTcyYThhNGI2NjU2MwBGAAAAAAAkp4jeTIsWQpRyZEj61wMmBwBc/S0jS+1UQ5vrIiugUidYAAAA6zbPAAA7UnQyV+J6T6aqh2OAoYlSAADUq9ZTAAA=




Why EwsId's are different?
(Note: EWS can't bind appointment object by EwsId from point 3)







c# outlook exchangewebservices






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 19 at 13:01

























asked Nov 19 at 12:20









ip.Nightly

33




33












  • What is the error when you try to use the id from #3?
    – Dmitry Streblechenko
    Nov 19 at 17:05










  • The error is "The specified object was not found in the store., The store ID provided isn't an ID of an item."
    – ip.Nightly
    Nov 20 at 4:06


















  • What is the error when you try to use the id from #3?
    – Dmitry Streblechenko
    Nov 19 at 17:05










  • The error is "The specified object was not found in the store., The store ID provided isn't an ID of an item."
    – ip.Nightly
    Nov 20 at 4:06
















What is the error when you try to use the id from #3?
– Dmitry Streblechenko
Nov 19 at 17:05




What is the error when you try to use the id from #3?
– Dmitry Streblechenko
Nov 19 at 17:05












The error is "The specified object was not found in the store., The store ID provided isn't an ID of an item."
– ip.Nightly
Nov 20 at 4:06




The error is "The specified object was not found in the store., The store ID provided isn't an ID of an item."
– ip.Nightly
Nov 20 at 4:06












1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










    0003240061663262376366642d646536392d343832362d623936322d373261386134623636353633004600000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000

0000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000

0003240061663262376366642d646536392d343832362d623936322d3732613861346236363536330046000000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000


So above I've converted you Ids to hex because this is probably the easiest way to explain it. The EWSId contains the PREntryId (along with a bunch of routing information which is documented so you should always use convertId to do the conversation) so you can see that 2,3 is that they are the same for the last portion of the Id. With the Id from 1 the PR_EntryId would be



000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000


and from the providerId in the above which is documented in https://msdn.microsoft.com/en-us/library/ee201952(v=exchg.80).aspx you can tell that those two items in question are in different mailboxes. So it sounds like maybe you may not understand how identifiers work eg the same appointment in two different mailboxes will have two different Identifiers because underlying they are two different objects in the Exchange Store. If your trying to relate items together use the Goid Properties like PidLidCleanGlobalObjectId (just google it for examples and explanations)






share|improve this answer





















  • Thank you very much. Yesterday my brain was like a limp bisquit. I got the first EwsId under User#1 credentials, but the second HexEntryId I got under User#2 credentials. That was a problem. Now ids are the same. Have a good day.
    – ip.Nightly
    Nov 20 at 4:24













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374516%2fconverting-hexentryid-of-appointmentitem-returns-ewsid-which-is-not-equal-unique%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote



accepted










    0003240061663262376366642d646536392d343832362d623936322d373261386134623636353633004600000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000

0000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000

0003240061663262376366642d646536392d343832362d623936322d3732613861346236363536330046000000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000


So above I've converted you Ids to hex because this is probably the easiest way to explain it. The EWSId contains the PREntryId (along with a bunch of routing information which is documented so you should always use convertId to do the conversation) so you can see that 2,3 is that they are the same for the last portion of the Id. With the Id from 1 the PR_EntryId would be



000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000


and from the providerId in the above which is documented in https://msdn.microsoft.com/en-us/library/ee201952(v=exchg.80).aspx you can tell that those two items in question are in different mailboxes. So it sounds like maybe you may not understand how identifiers work eg the same appointment in two different mailboxes will have two different Identifiers because underlying they are two different objects in the Exchange Store. If your trying to relate items together use the Goid Properties like PidLidCleanGlobalObjectId (just google it for examples and explanations)






share|improve this answer





















  • Thank you very much. Yesterday my brain was like a limp bisquit. I got the first EwsId under User#1 credentials, but the second HexEntryId I got under User#2 credentials. That was a problem. Now ids are the same. Have a good day.
    – ip.Nightly
    Nov 20 at 4:24

















up vote
0
down vote



accepted










    0003240061663262376366642d646536392d343832362d623936322d373261386134623636353633004600000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000

0000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000

0003240061663262376366642d646536392d343832362d623936322d3732613861346236363536330046000000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000


So above I've converted you Ids to hex because this is probably the easiest way to explain it. The EWSId contains the PREntryId (along with a bunch of routing information which is documented so you should always use convertId to do the conversation) so you can see that 2,3 is that they are the same for the last portion of the Id. With the Id from 1 the PR_EntryId would be



000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000


and from the providerId in the above which is documented in https://msdn.microsoft.com/en-us/library/ee201952(v=exchg.80).aspx you can tell that those two items in question are in different mailboxes. So it sounds like maybe you may not understand how identifiers work eg the same appointment in two different mailboxes will have two different Identifiers because underlying they are two different objects in the Exchange Store. If your trying to relate items together use the Goid Properties like PidLidCleanGlobalObjectId (just google it for examples and explanations)






share|improve this answer





















  • Thank you very much. Yesterday my brain was like a limp bisquit. I got the first EwsId under User#1 credentials, but the second HexEntryId I got under User#2 credentials. That was a problem. Now ids are the same. Have a good day.
    – ip.Nightly
    Nov 20 at 4:24















up vote
0
down vote



accepted







up vote
0
down vote



accepted






    0003240061663262376366642d646536392d343832362d623936322d373261386134623636353633004600000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000

0000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000

0003240061663262376366642d646536392d343832362d623936322d3732613861346236363536330046000000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000


So above I've converted you Ids to hex because this is probably the easiest way to explain it. The EWSId contains the PREntryId (along with a bunch of routing information which is documented so you should always use convertId to do the conversation) so you can see that 2,3 is that they are the same for the last portion of the Id. With the Id from 1 the PR_EntryId would be



000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000


and from the providerId in the above which is documented in https://msdn.microsoft.com/en-us/library/ee201952(v=exchg.80).aspx you can tell that those two items in question are in different mailboxes. So it sounds like maybe you may not understand how identifiers work eg the same appointment in two different mailboxes will have two different Identifiers because underlying they are two different objects in the Exchange Store. If your trying to relate items together use the Goid Properties like PidLidCleanGlobalObjectId (just google it for examples and explanations)






share|improve this answer












    0003240061663262376366642d646536392d343832362d623936322d373261386134623636353633004600000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000

0000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000

0003240061663262376366642d646536392d343832362d623936322d3732613861346236363536330046000000000024a788de4c8b164294726448fad7032607005cfd2d234bed54439beb222ba0522758000000eb36cf00003b52743257e27a4fa6aa876380a189520000d4abd6530000


So above I've converted you Ids to hex because this is probably the easiest way to explain it. The EWSId contains the PREntryId (along with a bunch of routing information which is documented so you should always use convertId to do the conversation) so you can see that 2,3 is that they are the same for the last portion of the Id. With the Id from 1 the PR_EntryId would be



000000001992182109ea3543a646f6311caa8f020700184109defd3dd44680080b202542aa1a00000000010d0000184109defd3dd44680080b202542aa1a0000285190830000


and from the providerId in the above which is documented in https://msdn.microsoft.com/en-us/library/ee201952(v=exchg.80).aspx you can tell that those two items in question are in different mailboxes. So it sounds like maybe you may not understand how identifiers work eg the same appointment in two different mailboxes will have two different Identifiers because underlying they are two different objects in the Exchange Store. If your trying to relate items together use the Goid Properties like PidLidCleanGlobalObjectId (just google it for examples and explanations)







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 19 at 21:15









Glen Scales

11.6k11016




11.6k11016












  • Thank you very much. Yesterday my brain was like a limp bisquit. I got the first EwsId under User#1 credentials, but the second HexEntryId I got under User#2 credentials. That was a problem. Now ids are the same. Have a good day.
    – ip.Nightly
    Nov 20 at 4:24




















  • Thank you very much. Yesterday my brain was like a limp bisquit. I got the first EwsId under User#1 credentials, but the second HexEntryId I got under User#2 credentials. That was a problem. Now ids are the same. Have a good day.
    – ip.Nightly
    Nov 20 at 4:24


















Thank you very much. Yesterday my brain was like a limp bisquit. I got the first EwsId under User#1 credentials, but the second HexEntryId I got under User#2 credentials. That was a problem. Now ids are the same. Have a good day.
– ip.Nightly
Nov 20 at 4:24






Thank you very much. Yesterday my brain was like a limp bisquit. I got the first EwsId under User#1 credentials, but the second HexEntryId I got under User#2 credentials. That was a problem. Now ids are the same. Have a good day.
– ip.Nightly
Nov 20 at 4:24




















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374516%2fconverting-hexentryid-of-appointmentitem-returns-ewsid-which-is-not-equal-unique%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Tonle Sap (See)

I get strange results when I access the Sqlitedatabase with Unity C# via XAMPP

Guatemaltekische Davis-Cup-Mannschaft