Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mail Message Delta list missing change type query parameter in 5.x #2195

Closed
idiotsky opened this issue Nov 2, 2023 · 2 comments · Fixed by #2227
Closed

Mail Message Delta list missing change type query parameter in 5.x #2195

idiotsky opened this issue Nov 2, 2023 · 2 comments · Fixed by #2227

Comments

@idiotsky
Copy link

idiotsky commented Nov 2, 2023

In 4.x we can write code like this.

IMessageDeltaCollectionPage messageDeltaCollectionPage = await graphServiceClient .Me.MailFolders[folderId] .Messages.Delta() .Request(new List<Option> { new QueryOption("$select", "LastModifiedDateTime"), new QueryOption("changeType", "created"), new HeaderOption("Prefer", $"odata.maxpagesize={MaxPageSize.ToString()}") }) .Filter($"receivedDateTime ge {syncAfter:s}Z") .GetAsync();

but in 5.x
graphServiceClient.Me.MailFolders[folderId].Messages.Delta.GetAsDeltaGetResponseAsync( configuration => { configuration.QueryParameters.Select = new[] { "LastModifiedDateTime" }; configuration.QueryParameters.Filter = $"receivedDateTime ge {syncAfter:s}Z"; configuration.Headers.Add("Prefer", $"odata.maxpagesize={MaxPageSize.ToString()}"); });
there's no place to specify the changetype like this
configuration.QueryParameters.ChangeType = new[] { "created", };

@andrueastman
Copy link
Member

Depends on resolution of microsoftgraph/msgraph-metadata#480

@baywet
Copy link
Member

baywet commented Nov 15, 2023

Update: the fix to metadata was just merged in today, which means the query parameter should show up in the next generation next week.
microsoftgraph/msgraph-metadata#500

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants