You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like .NET Graph SDK to support the full features of Graph (or, alternatively, I can't find the docs for what I need). I'd like to make a request to:
That is - I'd like to look at group membership, but filtered to only groups (ignoring users). The "isof" selector here is supported by the client library, but not the server. And, the casting ("/microsoft.graph.group") appears to be supported on the server but not in the client library. For this request, Graph Explorer shows sample code for .NET that corresponds to:
I experimented a little with the SDK based on some of the code in depot and eventually wrote:
var originalUrl = GraphClient
.Groups[groupId]
.Members
.RequestUrl;
Type t = typeof(Group);
return new GroupMembersCollectionWithReferencesRequestBuilder($"{originalUrl}/{t.FullName}", GraphClient)
.Request();
This way, the SDK would make the request, but deserialization was problematic. Because the Graph API does not return an @odata.type when it's specified by the caller, the .NET Graph SDK deserialized the response objects as if they were generic DirectoryObjects rather than Groups, which is not productive.
Describe the solution you'd like
I'd like to be able to write something like:
I'd like .NET Graph SDK to support the full features of Graph (or, alternatively, I can't find the docs for what I need). I'd like to make a request to:
OR
That is - I'd like to look at group membership, but filtered to only groups (ignoring users). The "isof" selector here is supported by the client library, but not the server. And, the casting ("/microsoft.graph.group") appears to be supported on the server but not in the client library. For this request, Graph Explorer shows sample code for .NET that corresponds to:
I experimented a little with the SDK based on some of the code in depot and eventually wrote:
This way, the SDK would make the request, but deserialization was problematic. Because the Graph API does not return an @odata.type when it's specified by the caller, the .NET Graph SDK deserialized the response objects as if they were generic DirectoryObjects rather than Groups, which is not productive.
Describe the solution you'd like
I'd like to be able to write something like:
Describe alternatives you've considered
I'll probably just not filter my results (extra bandwidth / latency, but the feature works).
AB#6678
The text was updated successfully, but these errors were encountered: