This post is over a year old, some of this information may be out of date.
Over the last couple of months I developed a calendar application that synchronized events from an external system to a user’s calendar in Office 365. For the event creation process I made use of the Microsoft Graph previous known as the Unified API which was still in beta at that time. During the beta of the Microsoft Graph API things have changed a couple of times. That meant that I had to update my application once they introduced breaking changes or new improvements and there were a couple of breaking changes introduced during this beta period. Today Microsoft announced the general availability of the Microsoft Graph. With the launch of this first official version of the Microsoft Graph API we can expect that the API will not involve breaking changes when updates happen.
The Microsoft Graph has now a versioned v1.0 endpoint and there were again a couple of new API changes. The biggest change for the event creation process is that the start and end properties should now include the DateTime and TimeZone of the event. Durign the beta period you only had to pas the DateTime.
Note: here are some references to the latest Unified API changes:
Of course with these API property changes I had to update the application once again to change all the beta endpoints to the new v1.0 endpoint and also the events creation process itself. While updating the event process code, I experienced some problems creating all day events. This article explains where you need to pay attention to in order to correctly create an all day event.
Note: the same code can be used to create regular events.
Event creation problems
The creation process of these events is not that hard at all. You only have to call the right endpoint and pass your event values.
The problem I struggled with was creating the event with the right time zone in order that it was displayed correctly in Outlook. The application itself was built with MVC and the creation of the events was done via C#. I used a library called RestSharp (http://restsharp.org/) that makes using REST and HTTP API calls in .NET easier.
My model before the change looked like this:
I had to change the start and end properties in order to include the time zone.
Once I made this change to my event model, I start experiencing two problems:
- I got an event creation error: the start and end times for an all-day event need to be set to midnight;
- When the event eventually got created, it was not created with the right time zone. The event was spread over two days in Outlook.
The start and end times for an all-day event need to be set to midnight
As the first problem itself describes, you have to set the start and end properties of the event to midnight. So first of all you need to be sure that the DateTime object is correctly set:
Now this was not enough, I kept receiving the error. When I checked my serialized JSON object, I saw that it had taken the time zone into account, although it was not specified on the DateTime object.
What I noticed was that RestSharp always serialized the DateTime object to UTC format (indicated by the “Z” suffix) and took the current time zone into account. To solve this I switched to make use of the Newton serializer. By making use of the Newton serializer the DateTime objects were serialized correctly:
So be aware that your start and end properties contain the right values the API expects.
All day events that spread over two days
This had to do with the time zone in which the event gets created. You need to be sure that you are using the same time zone your user’s calendar is set. At the moment there is no API available to get the time zone information.
Here is the code I used to create the all day events:
This is what the create function does:
The JSON object looks like this: