-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@microsoft.graph.conflictBehavior
in driveitem copy
#981
Comments
@microsoft.graph.conflictBehavior
in file copy@microsoft.graph.conflictBehavior
in driveitem copy
I'm trying this aswell using the Graph API and it always returns nameAlreadyExists regardless of the behaviorConflict specified
How to work around this ?? |
any updates? |
come on guys? |
I can also confirm that this still does not function properly. |
Adding @microsoft.graph.conflictBehavior=rename to query string parameters did work for me |
as @marcogiannetta said, you have to add to the query params. If you're using the C# Graph SDK you have to send a query option on the request.
|
Well docs should be updated then |
It looks like the workaround above only works for OneDrive for Business... OneDrive Personal still seems to ignore it. |
Adding @microsoft.graph.conflictBehavior to query string doesn't work either: Edit: It actually works, my bad. I just had different unrelated error (overwrite is not supported for folders) |
Does not work with the personal accounts. 😒 |
As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness. |
Category
Expected or Desired Behavior
Copying a driveitem allows for defining
@microsoft.graph.conflictBehavior
to handle conflicts, as per design according to issue #759This should also be documented.
Observed Behavior
Conflicts cause
409 Conflict
response despite@microsoft.graph.conflictBehavior
.Steps to Reproduce
^ Making this request twice will cause
409 Conflict
nameAlreadyExists
on the second try.The text was updated successfully, but these errors were encountered: