Microsoft 365 Community Microsoft Graph, 1 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Introduction to Microsoft Graph .Net SDK v5

Description

In this 8-minute developer focused demo – Andrew Omondi shares SDK, generated by the new code generator called Kiota, v5 enhancements that enrich the developer’s experiences across Microsoft Graph. Enhancements include Backing store (object tracking), support $count endpoints, support for OData Cast endpoints and Parameter objects. Appreciate differences between v4 and v5 calls, improvements in Intellisense, increased performance due to smaller payloads, newly supported endpoints, fewer lines of code for greater capability, etc. The SDK is in preview and feedback is very welcome. This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on June 14, 2022.

Demo Presenter
• Andrew Omondi (Microsoft)

Supporting materials
• Repo – Project Kiota | aka.ms/Kiota
• Repo - Microsoft Graph .NET SDK v5 changelog and upgrade guide | aka.ms/graph/sdk/dotnet-preview

Learn more
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - http://aka.ms/m365/community

A

Hey everyone, my name is andrew and I'm from the graph developer experiences team. So today I just wanted to talk a bit about the graph.net v5 sdk, that we are working on right now and we're just hoping to address some of the few changes that we're making and enhancements uh to enrich the user experiences.

A

That's going to help us make it a better experience for everyone, so the new version of the sdk is generated with a new tool called kyoto.

A

uh So we've been working together, the team for the past few months to get this one up and running, and we have a few enhancements that have been coming in that enable us to make and do things that we couldn't really do before among them, which I will talk a bit about more later, is like the barking store and calling various endpoints like the auditor cast and their data account and the use of uh parameter objects.

A

So the first thing I wanted to talk about really is like the change of the developer experience and at the top of the slide, I can see what you would currently do to make a call with the v4 and the bottom, with the uh the new preview version of v5, and you notice like a couple of things, and one of them is like that. There is no longer the request function in the in the whole. Fluent api method called to make the the user sdk a bit more substantive as well as now.

A

The configuration of the request is done with like a lambda that is passed over to the get or post or purchasing method, and this really, with the help of accurate uh descriptions that we're getting from the various api owners, uh enables us to have like a rich experience with regards to the intellisense, because now like, for example, like the count there now is like a strongly typed parameter like it's a boolean or the select is like a collection of strings vis-a-vis there.

A

You need to figure out like whether how the string needs to be formatted and correct, and that would result in like various user errors when making uh calls to the graph.

A

So the next thing I also wanted to talk about was uh the barking stone and really the barking store is it enables like dirty tracking of the changes in various objects and, like you notice, like with version 4, the sdk like in a scenario where you're trying to like disable the recurrence over of an event.

A

uh Let's say you fetch the event and then you transfer the recurrence property to now and then send it back what you notice that really won't work, because uh the serializer won't really send out uh null values, but now with v5, we have this backing store that keeps track of changes. That's happening to the object uh when it comes back and therefore you should just be able to set the property to now and send it back, and that will sort out your issue. And since now we are also keeping track of the object.

A

We only send the properties that change, rather than the entire object as well, so that will result in like a smaller payload being sent out better efficiency, and we should probably notice better performance in whatever scenarios that you are working with.

A

I also wanted to talk about is now the use of a parameter object so like in a given scenario, where you are trying to maybe call the send mill api currently in version four. These uh parameters of the data function are literally function. uh Parameters of the ascend main function. So what now? What we've done is we've moved over to using a request body which is basically like a nested, is an object that nests this properties inside so like.

A

In this scenario, we have like a send mail post request body and therefore the message and the safe to send items parameters will be properties inside this object and therefore, with this, you just pass the object over to the post method and, in the event like when the api endpoint has changed, or the api evolves to maybe introduce like new parameters to the to the api.

A

This doesn't result in like clients having breaking changes or running into issues, because the small function has added new parameters and therefore this results to like better user experience for everyone and a cleaner uh solution uh for everyone that is trying to use the sdk.

A

Finally, I just was hoping to talk about like a couple of uh scenarios that weren't really supported in the current version of the sdk and the first one really was uh calling like the dollar count, endpoints or account segments or data. So this is a scenario like whereby you're trying to like get the number of users in your tenant or something so uh you just want to get that as an integer and get it back into your app to figure out what you want to do next. uh So you can't really do this.

A

You really have to probably build the url yourself and make your own native http request, but now, with the use of kyoto and using the generated sdk, you can just use this single line of code to configure request, get account and get that uh to use it. Then. The next scenario is the support for the auditor cast segment.

A

So this is where now you want to take api side filtering, especially for apis that give like a collection of different types of object. So let's say you want to get members of the group and the members of the group could be users or applications or any other type. So with the new version 5 that we're working on in preview, you can just add the extra segment like to get like members that are users, and this will eliminate the need for you to do like client-side filtering and add all that logic.

A

That would make life a bit harder for you, so you can just follow the link. There are a lot of other changes that we are working on, so the link will lead you to detailed changes of things that are going on the new version. It's in preview. We are looking for feedback from everyone, so please give us feedback on github and let us know what we can do to make it better. uh With the current version, uh we are going to continue supporting it with metadata updates quickly, as we continually do.

A

That's it for me I'll hand it over to brand. Thank you so much andrew great to hear about the updates coming for the.net sdk, for this.