microsoftgraph / microsoftgraph/msgraph-sdk-java
Copying File to another sharepoint destination
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Java
- Estrellas
- 444
- Forks
- 154
- Merge medio
- 18 h 28 min
- PR fusionados (30 d)
- 4
Descripción
Describe the bug
HI ,
I am copying a file from my sharepoint site to another location on the same site.
The first time i execute the code the file is copied correctly.
When i change the file content in the source folder and copy it again the code executes without errors but
the new file is not copied. In the destination folder there is still the file that was initialy copied.
I read the docs : https://learn.microsoft.com/en-us/graph/api/driveitem-copy?view=graph-rest-1.0&tabs=http
According to the docs i can use @microsoft.graph.conflictBehavior to replace the file in the destination but this does not work. The file is only copied once. When i delete the file in the destination the file is copied again.
This is the code i use.
Be sure that the referenced ids in the snipplet are fine and that in copyPostRequestBody the copyPostRequestBody.setParentReference(itemRefDestination); is set correctly.
DriveItem created = authenticationProvider.getGraphServiceClient().drives().byDriveId(driveRoot.getId()).items()
.byDriveItemId(driveItem.getId()).copy()
.post(copyPostRequestBody);
The other question i have here is: Why is "DriveItem created" always null ? According to the SDK post(...) returns a DriveItem. No matter if the copy is made (in the first place) or not the returned object is always null.
How can i make sure that changes made on the file in the source folder are always copied?
Expected behavior
I expect the file to be copied and the conflict behaviour provided is applied. As in when "replace" than its replaced , when "rename" the file is renamed in the destination.
How to reproduce
// get the source file as DriveItem
DriveItem sourceItem= driveItemManager.getDriveItemByPath(source.getPath());
// get the destination location as DriveItem
DriveItem destinationRoot = driveItemManager.getDriveItemByPath(destination.getPath());
// create ItemReference from destination root.
ItemReference itemRefDestination = new ItemReference();
itemRefDestination.setDriveId(driveItemDest.getParentReference().getDriveId());
itemRefDestination.setId(driveItemDest.getId());
itemRefDestination.setName(destination.getName());
// create CopyPostRequestBody and set reference.
CopyPostRequestBody copyPostRequestBody = new CopyPostRequestBody();
copyPostRequestBody.setParentReference(itemRefDestination);
//execute the copy call -> myDriveId
DriveItem post = authenticationProvider.getGraphServiceClient().drives().byDriveId(myDriveId).items()
.byDriveItemId(sourceItem.getId()).copy()
.post(copyPostRequestBody);
SDK Version
6.33.0
Latest version known to work for scenario above?
5.80.0
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
Windows 11
### Other information
_No response_
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza con el punto de entrada DriveItem copy().post(...) y la documentación de Microsoft Graph driveItem copy enlazada en el issue. Reproduce el escenario usando el código proporcionado de source, destination, ItemReference y CopyPostRequestBody, y determina después por qué no se aplica el reemplazo y por qué post() devuelve null. Se considera terminado cuando el comportamiento de copia informado y el valor devuelto están explicados o corregidos.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- api, cloud
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100