Unable to get OpenTypeExtensionProperty for event using Graph API

Question

For one of our application, I am trying to get Extensions for an event using the following code in C#:

var result = graphServiceClient.User[userid].Calendar.Events[eventid].Extensions.Request().GetAsync().Result;

However, I am getting following exception:

Code: ErrorInvalidRequest
Message: The OData request is not supported.
ClientRequestId: f7a44c2f-ca79-4f79-9726-2cdc98d87e00

We need to add and get opentype extensions. Can somebody please help?

Answer 1

You can do this in two steps...
(1) Create an event and add opentypeextension part of it
(2) Get the event/opentypeextension

First, i used Microsoft Graph explorer to create the event. I made sure to add opentypeextension to it:

Then get the opentypeextensions for the above event using its id:

So my code would look like the below:

GraphServiceClient graphClient = new GraphServiceClient( authProvider );  
  
var extension = await graphClient.Me.Events["'AAMkAGRlNWYmM5YjIzNTRhMwBGAAAAAAA-AAA='"].Extensions["Com.Contoso.Referral"]  
    .Request()  
    .GetAsync();  
  

Answer 2

The above worked for me, however in my case I wanted to check all outlook events for the specific extension and in case the extension is not present in any one of the events, I was get the following error:

Code: ErrorItemNotFound

Message: The specified object was not found in the store.
ClientRequestId: a65d0d31-123b-4834-9bec-8d471d22b6e0

To resolve above, while iterating through all events I added the code for fetching extension in try catch block and added following code in catch block to continue the loop in case we have above exception

 if (ex.InnerException.GetType() == typeof(ServiceException) &&
                        ex.InnerException.Message.Contains("Code: ErrorItemNotFound"))
                        continue;

Anyways my issue is resolved now. Thanks for the help

Answer 3

Glad that the above helped you moving forward. Yes, you get the error as the extension not available in the items/store. I see that you have a workaround to move forward.