Fix "Find in this list" Search in Unified View find a record in the results beyond 1,500 limit.
Unified view query cannot search the RESULT beyond record number 1500 and requires you to export to search. I can understand the potential limit of VIEWING beyond 1500 but the search should be able to find a record that would be in the results regardless of the VIEWING limit. This makes query VERY LIMITED, since we test to make sure records one expects qualify within the parameters in criteria. Imagine having to export after EVERY tweak in a query, or ADAPTING the output to try and CAPTURE the name. Completely unnecessary extra work. FIX the search to find items in the result even if the list is beyond 1500. For example, I had a query I KNEW the person should be in the list and the result didn't find the person. Wasted so much time and when it was checked in database view - there was the name in the results. We cannot move to Unified view with confidence if BASIC SEARCH within query is limited to this degree.
-
Guest
- Jan 26 2026
- Reviewed: Voting Open
Related ideas
Echoing my support for this idea!
Echoing others who mention the balance of time/ease of viewing, but the ability should still be there. May be related to a case we have where we can't post more than 1000 transactions to any posting run. Give us the freedom to run a query for however long we want it to run, knowing that it might crash our browser window and we lose all the other things we are currently doing in the process. The annoying note that your download would be ready soon is an option of another way to do that.
We must have the ability to look at all the results in a query similar to what we can see in the database view - we can't lose functionality just because we are going to the unified view
Adding my voice here as well. Being able to view all records in a query is a critical part of validating results, reviewing data, and performing cleanup work. Many of us rely on Query specifically because it allows us to work directly from the results—opening records, correcting data, and confirming that our criteria are functioning as intended. Capping visibility at 1,500 records removes a core piece of that workflow.
If the system truly cannot display all results for performance reasons, then at the very least the search function must be able to search the full result set, not just the first 1,500 records. When we know a record should qualify but the Unified View search can’t find it—even though it appears in Database View—that undermines confidence in the tool and forces unnecessary exports after every small adjustment.
Unified View cannot replace Database View until either:
all results can be viewed, or
search can reliably find any record that qualifies, regardless of where it falls in the list.
Right now, neither is possible, and that creates significant friction for reporting, segmentation, and data maintenance.
While understand that the reason behind this limitation may have been to decrease the amount of time it takes for Query to load, there are definitely circumstances where we do need to be able to access all the records in the query results. I would be 100% on board with, when you scroll to the 1500th record in the query if there was a button to "load remaining results" and there could even be a pop up that let you know this may take longer than usual and you click ok to proceed.
So many times we're running large queries to either - check that specific records are in the results so we can adjust the query if not (to use the query for exports and reports) - OR (and this is the big one for me) - we are using query to identify and clean up records. Do I love that sometime there are more than 1500 records to clean up? No. But exporting to query for these is not an adequate work-around, as I need to be able to access those records FROM the query to do the necessary clean-up.
We really do need to have all the results visible in the query - there are so many cases when this is actually necessary and it needs to be fixed in Unified View to adequately support users data reporting, maintenance, and cleaning needs.
I didn't know this! Why would the search not go beyond 1500? We need this fixed!
💯