Skip to content

driveitem-move.md

Latest commit

 

History

History
152 lines (110 loc) · 5.47 KB

driveitem-move.md

File metadata and controls

152 lines (110 loc) · 5.47 KB
author spgraph-docs-team
ms.date 09/10/2017
title Move a driveItem to a new folder
ms.localizationpriority medium
ms.subservice sharepoint
description To move a driveItem to a new parent item, your app requests to update the parentReference of the driveItem to move.
doc_type apiPageType

Move a driveItem to a new folder

Namespace: microsoft.graph

To move a driveItem to a new parent item, your app requests to update the parentReference of the DriveItem to move.

It is a special case of the Update method. Your app can combine moving an item to a new container and updating other properties of the item into a single request.

Items cannot be moved between Drives using this request.

[!INCLUDE national-cloud-support]

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

[!INCLUDE permissions-table]

[!INCLUDE app-permissions]

HTTP request

PATCH /drives/{drive-id}/items/{item-id}
PATCH /groups/{group-id}/drive/items/{item-id}
PATCH /me/drive/items/{item-id}
PATCH /sites/{site-id}/drive/items/{item-id}
PATCH /users/{user-id}/drive/items/{item-id}

Request headers

Name Description
Authorization Bearer {token}. Required. Learn more about authentication and authorization.
Content-Type application/json. Required.
if-match String. If this request header is included and the eTag (or cTag) provided doesn't match the current eTag on the folder, a 412 Precondition Failed response is returned.

Request body

In the request body, supply the new value for the parentReference property. Existing properties that aren't included in the request body maintain their previous values or be recalculated based on changes to other property values. For best performance, you shouldn't include existing values that don't change.

Note: When moving items to the root of a drive, your app can't use the "id:" "root" syntax. Your app needs to provide the actual ID of the root folder for the parent reference. For example, /drives/{drive-id}/root.

Response

If successful, this method returns a 200 OK response code and updated driveItem resource in the response body.

Example

This example moves an item specified by {item-id} into a folder in the user's drive with the ID new-parent-folder-id.

HTTP

PATCH https://graph.microsoft.com/v1.0/me/drive/items/{item-id}
Content-type: application/json

{
  "parentReference": {
    "id": "{new-parent-folder-id}"
  },
  "name": "new-item-name.txt"
}

C#

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Go

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Java

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

JavaScript

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

PHP

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

PowerShell

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Python

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

Response

The following example shows the response for this move request.

HTTP/1.1 200 OK
Content-type: application/json

{
  "id": "0123456789abc",
  "name": "new-item-name.txt",
  "parentReference":
  {
    "driveId": "11231001",
    "path": "/drive/root:/Documents",
    "id": "1231203102!1011"
  }
}

Error responses

See Error responses for more info about how errors are returned.