langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-22 04:25:29 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Metadata deleted when selection spans 2+ pages #20344

New Issue
Closed
opened 2026-02-21 20:06:56 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:06:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Nov 15, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Create a knowledge base with more than 10 documents.
  2. Add custom multiple metadata keys to KB
  3. Select all documents on page one.
  4. Use metadata button to add one of the custom metadata keys
  5. Go to page and select some documents
  6. While on page 2 with 10+ items selected (10 from page 1) use the metadata tagging function again.
  7. Add the custom metadata

✔️ Expected Behavior

Documents selected on pages other than current one, should not lose other metadata values

❌ Actual Behavior

Every metadata that existed is deleted for elements not in the current page

Originally created by @DavideDelbianco on GitHub (Nov 15, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Create a knowledge base with more than 10 documents. 2. Add custom multiple metadata keys to KB 3. Select all documents on page one. 4. Use metadata button to add one of the custom metadata keys 5. Go to page and select some documents 6. While on page 2 with 10+ items selected (10 from page 1) use the metadata tagging function again. 7. Add the custom metadata ### ✔️ Expected Behavior Documents selected on pages other than current one, should not lose other metadata values ### ❌ Actual Behavior Every metadata that existed is deleted for elements not in the current page
yindo added the 🐞 buggood first issue labels 2026-02-21 20:06:56 -05:00
yindo closed this issue 2026-02-21 20:06:56 -05:00
yindo commented 2026-02-21 20:06:56 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 15, 2025):

This is a confirmed bug in Dify v1.9.2: when you select documents across multiple pages and apply metadata changes, existing metadata for documents not on the current page is lost. This happens because the frontend only has metadata for the currently loaded documents, so when it sends the batch update, it overwrites the entire metadata for documents from other pages with only the new values, erasing anything not present in the update. The backend then replaces the whole metadata set for each document with what it receives, which causes the loss of previous metadata values for documents not loaded in the current view.

A robust fix would require the frontend to fetch all selected documents' metadata before applying changes, or for the backend to support merging metadata instead of replacing it entirely. Until this is addressed, be cautious with multi-page selections and consider applying metadata changes page by page to avoid data loss.

You can see the relevant logic in the frontend and backend here:

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 15, 2025): <!-- Answer --> This is a confirmed bug in Dify v1.9.2: when you select documents across multiple pages and apply metadata changes, existing metadata for documents not on the current page is lost. This happens because the frontend only has metadata for the currently loaded documents, so when it sends the batch update, it overwrites the entire metadata for documents from other pages with only the new values, erasing anything not present in the update. The backend then replaces the whole metadata set for each document with what it receives, which causes the loss of previous metadata values for documents not loaded in the current view. A robust fix would require the frontend to fetch all selected documents' metadata before applying changes, or for the backend to support merging metadata instead of replacing it entirely. Until this is addressed, be cautious with multi-page selections and consider applying metadata changes page by page to avoid data loss. You can see the relevant logic in the frontend and backend here: - [Frontend batch metadata edit logic](https://github.com/langgenius/dify/blob/4a89403566c85eff76a959bc62be76f1e8af5ce6/web/app/components/datasets/metadata/hooks/use-batch-edit-document-metadata.ts#L16-L146) - [Backend metadata update logic](https://github.com/langgenius/dify/blob/4a89403566c85eff76a959bc62be76f1e8af5ce6/api/services/metadata_service.py#L201-L237) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0686f112-9fdb-4384-b4cf-f72241e2bd42?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0686f112-9fdb-4384-b4cf-f72241e2bd42?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0686f112-9fdb-4384-b4cf-f72241e2bd42?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0686f112-9fdb-4384-b4cf-f72241e2bd42?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0686f112-9fdb-4384-b4cf-f72241e2bd42?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0686f112-9fdb-4384-b4cf-f72241e2bd42?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0686f112-9fdb-4384-b4cf-f72241e2bd42?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28252)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label good first issue 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#20344
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?