# IRPCValueLists.RemoveValueListItemFromClient

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Vault API](https://developer.m-files.com/APIs/gRPC-API/vault/index.md) > [Value lists](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCValueLists/index.md)

HTML version: https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCValueLists/RemoveValueListItemFromClient/

Badges: `Vault API / core` `write` `session or assertion` `returns metadata structure version`

Deletes a traditional folder (marks it deleted).

- **Service:** [Value lists](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCValueLists/index.md) `MFiles.IRPCValueLists`
- **gRPC method:** `/MFiles.IRPCValueLists/RemoveValueListItemFromClient`
- **HTTP (mf-http-grpc):** `POST /grpc/v1/remove-value-list-item-from-client`
- **Request:** [`RemoveValueListItemFromClientRequest`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCValueLists/RemoveValueListItemFromClient/index.md#request)
- **Response:** [`RemoveValueListItemFromClientResponse`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCValueLists/RemoveValueListItemFromClient/index.md#response)
- **Book and level:** Vault API, core
- **Kind:** write
- **Session:** Required: a session (mfiles-session-id-bin metadata) or a session assertion (x-mf-session-assertion metadata).
- **Idempotent:** no
- **Returns metadata structure version:** yes (in the mfiles-metadata-version-bin trailer)
- **Streaming:** none (unary)

<a id="remarks"></a>

## Remarks

- Works only for Traditional folders (value list 4); other lists fail with "Access denied.".
  `allow_removing_owned_items` must be false; true also fails with "Access denied.".
- Requires the vault rights `license_allows_modifications` and `manage_traditional_folders`,
  and read access to the folder.
- Related: [RemoveOrDestroyTraditionalFolder](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCValueLists/RemoveOrDestroyTraditionalFolder/index.md)
  also handles the folder's contents.

<a id="request"></a>

## Request: RemoveValueListItemFromClientRequest

> Nested message fields are expanded to depth 3; follow a type link for deeper levels and for the type's own page.

| Field | Type | Description |
|---|---|---|
| `obj_id` | [`ObjID`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.ObjID/index.md) | The folder: `type` 4 and the folder's item ID. |
| `obj_id.type` | `int32` | The object type ID, for example 0 for documents. In a lookup value, the value list ID (for a lookup to objects, the object type ID). |
| `obj_id.item_id` | [`ItemID`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.ItemID/index.md) | The ID of the object within its type, in `item_id.internal_id`. |
| `obj_id.item_id.internal_id` | `int32` | The ID of the object or value list item. |
| `obj_id.item_id.external_repository_id` | [`ExternalRepositoryID`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.ExternalRepositoryID/index.md) | Used only for objects in external repositories (external connectors). Leave it unset for objects stored in the vault. |
| `allow_removing_owned_items` | `bool` | Must be false; the server rejects true with "Access denied.". |

<a id="response"></a>

## Response: RemoveValueListItemFromClientResponse

No fields.

<a id="related"></a>

## Related methods

- [RemoveOrDestroyTraditionalFolder](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCValueLists/RemoveOrDestroyTraditionalFolder/index.md): Deletes or destroys a traditional folder and everything in it.