Should it be possible to provide an $expand=singleValueExtendedProperties... query parameter on an events delta request? My approach returns an error that I wasn't quite expecting.
The request looks like this:
API:
https://graph.microsoft.com/v1.0
RESOURCE:
me/calendarView/delta
PARAMS:
startDateTime: 2020-07-01T00:00:00Z
endDateTime: 2021-12-31T23:59:59Z
$expand: singleValueExtendedProperties($filter=id eq 'Boolean {00062002-0000-0000-c000-000000000046} Id 0x00008229')
The request fails, returning this message in the body:
Parsing OData Select and Expand failed: Value cannot be null.
Parameter name: initialState
It's unclear which value that is referring to, though given that the error does not happen when omitting the $expand I suspect it has something to do with trying to expand in a delta query, or specifying an expand on this/andy extended property.
Omitting the $expand results in a successful response, and I am omitting the $deltatoken parameter to create a new stream (because existing streams are not encoded with the $expand).
You'll nice that the expand is on a non-string type MAPI property, specifically it is the Invited property. It's explicitly documented that you cannot $select properties that are not tracked, but it doesn't mention whether or not they can be included in the delta response itself.
Is this supposed to be possible? If so, can you point in my the right direction for formatting this request? Thanks!
Regarding this adjacent question that has already been asked. Seems out of date per the following.
The Get delta for Messages explicitly states that $expand is supported, but the Get delta for Events does not explicitly state anything about $expand, or any OData at all, it just states that $select is not supported.
If there is some hidden restriction, can it just be explicitly documented in the events delta documentation?
The error you are receiving is actually a bug in the library the service is using, see this issue and that issue.
You should be receiving an error saying that the request is not supported.
Even when the parsing bug gets fixed, it's unlikely to work as schema and open extensions are stored in another system than the resource and providing a unique delta token containing a watermark valid for both systems is not implemented today. You can request support for it on uservoice.