Closed thanhnguyen0504 closed 10 months ago
Hello thanhnguyen0504, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
Thanks for raising this @thanhnguyen0504 and also thanks for the research and pointer on $count and the consistency level.
Would you mind submitting a PR for this? The small internal team we have is working hard to get our v3.0.0 release ready for GA.
The one thing I will say is that using the eventual consistency header approach is that is an expensive call and will increase the likelihood of throttling within that tenant, so I'd prefer a solution that added a way for these additional parameters to be added only when the developer explicitly enables that mode of calling Graph.
This should have been fixed since the release of v3. Please update your app and report back here here you think we should reconsider it. Thanks!
Describe the bug
To Reproduce Steps to reproduce the behavior:
` <> <PeoplePicker selectedPeople={filteredPickedPeople} showMax={5} userType={UserType.user} userFilters="userType ne 'Guest'" selectionChanged={onSelectionChanged} className={getMgtClassName(themeInfo.themeName)}
curl 'https://graph.microsoft.com/v1.0/users?$top=6&$filter=userType%20ne%20%27Guest%27' \ -H 'Accept: */*' \ -H 'Accept-Language: vi-VN,vi;q=0.9,en-US;q=0.8,en;q=0.7,fr-FR;q=0.6,fr;q=0.5' \ -H 'Authorization: Bearer cannotsharewithyou\ -H 'Connection: keep-alive' \ -H 'Origin: https://teamsappstage.limeade.io' \ -H 'Referer: https://teamsappstage.limeade.io/' \ -H 'SdkVersion: MGT-PEOPLE-PICKER/2.9.0, MgtTeamsMsal2Provider/2.9.0, mgt/2.9.0, graph-js/2.2.1 (featureUsage=6)' \ -H 'Sec-Fetch-Dest: empty' \ -H 'Sec-Fetch-Mode: cors' \ -H 'Sec-Fetch-Site: cross-site' \ -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36' \ -H 'client-request-id: 577b7913-d416-e88f-55d9-67b8654c946f' \ -H 'sec-ch-ua: "Chromium";v="110", "Not A(Brand";v="24", "Google Chrome";v="110"' \ -H 'sec-ch-ua-mobile: ?0' \ -H 'sec-ch-ua-platform: "Windows"' \ --compressed
{"error":{"code":"Request_UnsupportedQuery","message":"Unsupported or invalid query filter clause specified for property 'userType' of resource 'User'.","innerError":{"date":"2023-03-02T08:12:56","request-id":"aea3b0e1-c57d-4d81-9c46-950e4c4cb470","client-request-id":"577b7913-d416-e88f-55d9-67b8654c946f"}}}
Expected behavior Should not return error and should show all users if I click to searchbox with empty text
Screenshots
I'm using PeoplePicker
This is the issue
Environment (please complete the following information):
Additional context Add any other context about the problem here.