Assigned
Status Update
Comments
bl...@google.com <bl...@google.com> #2
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
,directory-api ,users-list ,next-page-token ,query-parameter ,org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
br...@strataprime.com <br...@strataprime.com> #3
Automated by Blunderbuss job workspace-devrel-public-issue-tracker-blunderbuss-autoassigner for config assign for component 191635.
br...@workspaceadmins.org <br...@workspaceadmins.org> #4
nextPageToken randomly disappear depending on the query.
It's only returned if there is another page.
Also the starts with operator doesn't work on orgDepartment :
Can you open another bug for this.
je...@sixfive.io <je...@sixfive.io> #5
It's only returned if there is another page.
If less result than the page size, the nextPageToken doesn't exists instead to be null ?
Can you open another bug for this.
br...@strataprime.com <br...@strataprime.com> #6
If less result than the page size, the nextPageToken doesn't exists instead to be null ?
For any Google API, always check the truthiness of values as the underlying transport implementation may leak through (sometimes on purpose allowing customers to use gRPC) by a default value in a proto not being filtered/translated correctly.
er...@zalando.de <er...@zalando.de> #7
Comment has been deleted.
Description
Before opening a new issue, please search for other related issues , click the ★ to subscribe to updates, and click
+1
to vote.Description
Today in order to get reporting around Google Gemini usage a user must login to the admin portal and manually download the reports. This is slow, labor intensive, and makes collecting useful data around Gemini usage cumbersome. Opening this up to an API would allow us to automatically ensure we pull relevant data and consolidate it for analysis without having to login to the admin console every single day.
Impact
There is still little data available to us around Gemini usage, but having this data available via API makes it easier to collect the data en masse and allow us to process it in a meaningful way to start to glean insights around how effective the tooling is for our workforce.