You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug: Copy/Paste Feature Fails for Referenced Fields Collections
Describe the bug
The new copy/paste feature for schemas fails when trying to copy sections containing referenced fields, specifically when the reference is a collection of items (like FAQs). The error occurs even though the referenced documents exist in the dataset.
To Reproduce
Create a section with referenced fields (e.g., FAQ section referencing a collection of FAQ items)
Try to copy the section using the new copy/paste feature
Attempt to paste the section
Receive error toast: "Invalid clipboard item. The referenced document '[ID]' does not exist"
Expected behavior
The section should copy and paste successfully, maintaining the references to the existing FAQ items.
Error Screenshot
Sanity Versions
@sanity/cli (global) 3.54.0 (latest: 3.68.3)
@sanity/document-internationalization 3.3.0 (up to date)
@sanity/eslint-config-studio 5.0.1 (up to date)
@sanity/vision 3.68.3 (up to date)
sanity 3.68.3 (up to date)
Additional context
Verified through Vision tab with GROQ that the referenced document IDs exist in the dataset
Current workaround: None identified
Environment:
Node.js version: v21.4.0
bun version: 1.1.26
OS: macOS Sequoia (Version 15.1.1)
The text was updated successfully, but these errors were encountered:
Bug: Copy/Paste Feature Fails for Referenced Fields Collections
Describe the bug
The new copy/paste feature for schemas fails when trying to copy sections containing referenced fields, specifically when the reference is a collection of items (like FAQs). The error occurs even though the referenced documents exist in the dataset.
To Reproduce
Expected behavior
The section should copy and paste successfully, maintaining the references to the existing FAQ items.
Error Screenshot
Sanity Versions
Additional context
Environment:
The text was updated successfully, but these errors were encountered: