Getting some data from Microsoft Graph unified OData endpoint

Question

How to count number of items in EntitySet of MicrosoftGraph, for example 'users' or 'groups'? I tried:
- https://graph.microsoft.com/v1.0/users?$count Returns: lists all users
- https://graph.microsoft.com/v1.0/users/$count Returns: { "error": { "code": "Request_BadRequest", "message": "Unexpected segment Edm.Int32.", } }

Also in Annotations of target "microsoft.graph.directoryObject" which are those EntitySets based on I see that it is Selectable=false, Countable=false ...

Will $skip be ever available on 'users' or other toplevel EntitySet items ( https://graph.microsoft.com/v1.0/groups?$skip=5 ) ? It is available on other items ( https://graph.microsoft.com/v1.0/me/contacts?$skip=5 ). I know about $skipToken, but it is not the same.
Can I find somewhere in the $metadata if property is sortable? For example user.displayName is sortable, but user.mail or user.givenName are not. This would be handy in the $metadata. Is there plan to introduce this into $metadata?
OrderBy DESC in this formula https://graph.microsoft.com/v1.0/users?$orderBy=displayName%20desc is ignored, it shows items ordered ASC, am I doing something wrong?

Jon Knight Jon Knight · Accepted Answer · 2016-02-15T17:52:21

Not much help I know, but if you do an API call that gets a Collection you can get a count using the second form you gave in the first question. Eg:

https://graph.microsoft.com/v1.0/users/<id>/events/$count

returns the count (6 in my case, and not in JSON - the returned data is actually "\x{ef}\x{bb}\x{bf}6" (in Perl formatting)). If we use the ? as the last separator (which is what http://graph.microsoft.io/en-us/docs/overview/query_parameters seems to indicate we should) with this URL:

https://graph.microsoft.com/v1.0/users/<id>/events?$count

I just get the list of events with no count as you do.

So that seems to indicate two things to me:

a) The $count doesn't appear to work as a query parameter, despite the documentation and the OData standards saying it should,

and

b) There seems to be a bug in the API for handling EntitySets which isn't there for Collections.

Sorry I can't be of more help, but its another data point at least (I just came unstuck with the same thing which is why I noticed this StackOverflow post!)

Getting some data from Microsoft Graph unified OData endpoint

2 Answers