Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limiting documents in document pane to 2000 #6960

Open
TautvydasDerzinskas opened this issue Jun 17, 2024 · 1 comment
Open

Limiting documents in document pane to 2000 #6960

TautvydasDerzinskas opened this issue Jun 17, 2024 · 1 comment

Comments

@TautvydasDerzinskas
Copy link

Describe the bug

Right now there is intentionally set a limit of documents accessible in studio document pane list: 2000

However there is no mention of it in https://www.sanity.io/docs/technical-limits technical limits and if we have more than 2000 documents, it creates issues trying to view them

To Reproduce

Create a document type and add it to structure, so all documents could be loaded in document viewer pane/browser.
Create more than 2000 instances of the document.

Expected behavior

No limitations when scrolling document pane, or clearly mentioned documentation that for specific reasons there is a limit.

Screenshots
Screenshot 2024-06-17 at 16 51 52

Which versions of Sanity are you using?

@sanity/cli version 3.46.1 (project initialized with latest versions)

Security issue?

No

@runeb
Copy link
Member

runeb commented Jun 20, 2024

Hi @TautvydasDerzinskas. We limit the loading of this list for performance reasons. Our rationale is that is is not a very common user workflow to manually scroll thousands of documents in these lists, but instead use the built in or custom sort orderings to get relevant documents in view or filter the lists with search when you have much more than 2000 documents of a given type in a single Structure list.

Users also customize their Structure hierarchy to lay out documents in ways that fit the particular workflows of their editors, so a document type can be segmented by attributes such as categories or other metadata.

I'd love to hear more of about your particular use case! Do you think any of the above tips could help you lay out your Studio in a useful way to your editors?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants