microsoftgraph / microsoftgraph/msgraph-sdk-java

Copying File to another sharepoint destination

Open
#2,338 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status:waiting-for-triage type:bug
Dominant language
Java
Stars
444
Forks
154
Avg merge
18h 28m
Merged PRs (30d)
4

Description

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_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the DriveItem copy().post(...) entry point and the Microsoft Graph driveItem copy documentation linked in the issue. Reproduce the scenario using the provided source, destination, ItemReference, and CopyPostRequestBody code, then determine why replacement is not applied and why post() returns null. Done means the reported copy behavior and returned value are explained or corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.