Microsoft-graph-docs: API reference doesn't document conflictBehavior values

Created on 22 Nov 2016  路  4Comments  路  Source: microsoftgraph/microsoft-graph-docs

api-reference/v1.0/resources/driveitem.md doesn't document what the possible values of @microsoft.graph.conflictBehavior are.

api-reference/v1.0/api/item_createuploadsession.md mentions rename as one possible value, but doesn't say what happens if rename is not specified, or if there are any other possible values.

Most helpful comment

@marych can one please help me with @microsoft.graph.conflictBehavior?
It says (https://dev.onedrive.com/items/create.htm):
If @microsoft.graph.conflictBehavior is set to rename and an item with the same name already exists in the destination, the new item name will be updated to be unique. OneDrive will append a number to the end of the item name (for files - before the extension).
For example, My Folder would be renamed My Folder 1. If My Folder 1 is taken, then the number would be incremented again until a unique filename is discovered.
But when I'm trying to send the same request with same file name and with @microsoft.graph.conflictBehavior set to rename it is not creating any new folder instead returning the previously created file with HTTP status code 200.
Please comment on this..!

All 4 comments

@marych can one please help me with @microsoft.graph.conflictBehavior?
It says (https://dev.onedrive.com/items/create.htm):
If @microsoft.graph.conflictBehavior is set to rename and an item with the same name already exists in the destination, the new item name will be updated to be unique. OneDrive will append a number to the end of the item name (for files - before the extension).
For example, My Folder would be renamed My Folder 1. If My Folder 1 is taken, then the number would be incremented again until a unique filename is discovered.
But when I'm trying to send the same request with same file name and with @microsoft.graph.conflictBehavior set to rename it is not creating any new folder instead returning the previously created file with HTTP status code 200.
Please comment on this..!

Pull request #634 was merged.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

shyamkris picture shyamkris  路  3Comments

climam picture climam  路  4Comments

dcnoren picture dcnoren  路  4Comments

dagexiongfeng picture dagexiongfeng  路  4Comments

fredericklin picture fredericklin  路  3Comments