> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/ja/troubleshooting/causes-of-missing-content/empty-libraries/empty-document-libraries-for-managed-mappings.md).

# 管理対象マッピングの空のドキュメント ライブラリ

## 状況

現在、一部のお客様で、管理対象マッピングによってマッピングされたボリュームに対して、ドキュメント ライブラリにコンテンツが表示されない問題が発生しています。これらのユーザーの権限は変更されておらず、Edge ブラウザーでは正しく表示されます。

KONNEKT は GraphAPI を使用して、SharePoint Online からこれらのデータを取得します。この原因となっているクエリは、KONNEKT のログでこの行の前に見つかります:

```
[RESTkitClient] HTTP リクエスト (OneDriveClient::GetItemByPath) GET:
```

構造は次のようなものです:

```
https://graph.microsoft.com/v1.0/sites/TenantName.sharepoint.com:/sites/SiteName:/drive/root?$select=name
```

問題 [Microsoft SharePoint の GitHub リポジトリ](https://github.com/SharePoint/sp-dev-docs/issues/10313).

## **解決策**

次のバージョンにアップグレードしてください: [KONNEKT 2.11.2](https://docs.konnekt.io/ja/troubleshooting/causes-of-missing-content/empty-libraries/pages/ad8fcff1909cb51ba3bae241bfcee7c4560f8022#id-2.11.2-published-2025-08-04) 以降。

影響を受ける Graph API 呼び出しを使用しない軽減策を KONNEKT 2.11.2 に追加しました。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.konnekt.io/ja/troubleshooting/causes-of-missing-content/empty-libraries/empty-document-libraries-for-managed-mappings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.