microsoftgraph / microsoftgraph/msgraph-sdk-java
@microsoft.graph.sharedChanged annotation not set on folders in delta query with deltashowsharingchanges
Personne n'a encore pris cette issue.
- Langage dominant
- Java
- Étoiles
- 444
- Forks
- 154
- Merge moyen
- 18 h 28 min
- PR mergées (30 j)
- 4
Description
Description
When using the delta query API with Prefer: deltashowremovedasdeleted, deltatraversepermissiongaps, deltashowsharingchanges headers, the @microsoft.graph.sharedChanged OData annotation is only set on files, never on folders — even when folders appear in the delta response with a shared facet.
This is an API behavior issue, not SDK-specific, but we're filing here as the docs repo has issues disabled.
Steps to reproduce
-
Get a latest delta token:
GET /drives/{drive-id}/root/delta?token=latest Headers: Prefer: deltashowremovedasdeleted, deltatraversepermissiongaps, deltashowsharingchanges -
Share a file located inside a folder hierarchy (e.g.,
root/folder/sub-folder/sample.jpg) with a specific user. -
Query delta with the token from step 1:
GET /drives/{drive-id}/root/delta?token={token} Headers: Prefer: deltashowremovedasdeleted, deltatraversepermissiongaps, deltashowsharingchanges
Actual result
The response contains 4 items. Only the file has @microsoft.graph.sharedChanged, the parent folders do not:
FOLDER root — @microsoft.graph.sharedChanged: NOT PRESENT
FOLDER folder — @microsoft.graph.sharedChanged: NOT PRESENT, shared: {scope: users}
FOLDER sub-folder — @microsoft.graph.sharedChanged: NOT PRESENT
FILE sample.jpg — @microsoft.graph.sharedChanged: true, shared: {scope: users}
Expected result
Per the documentation:
"all items that appear in the delta query response due to permission changes have the @microsoft.graph.sharedChanged: True OData annotation"
Parent folders that appear as hierarchy context (not due to their own permission change) should either:
- Have
@microsoft.graph.sharedChangedset when they are directly shared, OR - Be excluded from the response when they are only hierarchy context
Currently, folders never receive the annotation regardless of whether they were directly shared or appear as parent hierarchy. This makes it impossible to distinguish parent folder noise from real folder permission changes.
Additional testing
Tested all header combinations against the same delta token:
| Headers | Result |
|---|---|
| deltashowremovedasdeleted, deltatraversepermissiongaps, deltashowsharingchanges | 4 items, annotation only on file |
| Same + hierarchicalsharing | Identical 4 items |
| Same + deltaExcludeParent: true | Identical 4 items |
| Only deltashowsharingchanges | Identical 4 items |
| No Prefer headers | 0 items |
Environment
- API version: v1.0
- Authentication: Application permissions (client credentials)
- Service: SharePoint Online
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Aucun fichier du dépôt ni aucun test n’est identifié ; commencez par le endpoint documenté /drives/{drive-id}/root/delta et les en-têtes Prefer indiqués, en utilisant la séquence de jetons fournie pour reproduire la réponse à quatre éléments. C’est terminé lorsque le comportement du service ou sa documentation distingue clairement les dossiers directement partagés des dossiers présents uniquement dans la hiérarchie, avec le comportement attendu des annotations vérifié.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Domaine
- api, cloud
- Type d'issue
- Bug
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Calme
- Clarté
- Plutôt claire
- Accessibilité débutants
- 25/100