Query in WebView is not a benefit for system administration or review at this point. We want users to adopt and utilize the system. If users have to export a list, leave the system, and then return to make updates, we have lost the opportunity to keep them working within the system.

If all results are available and searchable, users can access groups of information and see details that are not currently visible as options in Lists. They can also review and maneuver through the data more efficiently and make quick updates or changes directly to a record within the query. This keeps users in the system, makes the data more actionable, and provides a much more effective experience for administration and review. This is not only a need for clean up but just basic review of data activity.

This is critical. This is one of those areas that is slowing the adoption of the web view. I can do what I need to do in using queries in the database view. I can not in the web view. I also don't want to live in a world where I am constantly compromising my data by exporting it. I want and need to work within the database as much as possible.

Many organizations rely heavily on Query to identify groups of records that require review, cleanup, or updates. However, Query currently limits the number of results that can be viewed directly within the system.

Because of this limitation, users are forced to export query results to review the full dataset. Once exported, the workflow becomes highly inefficient:

• Users cannot open constituent records directly from the exported results

• Each record must be manually searched again in RENXT

• This process must be repeated record by record

This creates a significant disconnect between data identification (Query) and data maintenance (record updates).

Business Impact

This limitation results in:

• Major productivity loss for database teams

• Increased risk of data entry errors when re-searching records manually

• Slower data cleanup cycles

• Reduced adoption of Query for operational workflows

For organizations that use Query as a primary tool for data maintenance, this represents a substantial regression in usability and efficiency.

Expand Query View Limits

Allow users to:

• View all query results directly within the system

• Scroll through full datasets and easily maneuver to the end and beginning of the dataset

• Open records directly from the query results screen

The current Query limitations create unnecessary friction and significantly slow down routine database maintenance. Enabling full result viewing would dramatically improve efficiency and align Query with real-world usage needs.

Echoing what has been said: viewing all records in a query is essential for data maintenance and clean up. My team regularly utilizes query in this way. If we have to click a button to view more records, so be it.

I had no idea about this until I read a post online this morning. I haven't done a lot of queries in webview and given these circumstances, that's unlikely to change. Viewing all query results is so important to confirming a query was created and processed successfully. It's incredibly useful for investigating and efficiently correcting potential errors as well.

It is critical that we are able to work directly from query to open and correct records, no matter the size of the query. Many of us have large data clean-up projects that we do from within query. Export does not solve this problem and means having to search individually for each record to open them and work with them. That is incredibly inefficient and show a fundamental misunderstanding of how we use query. It's absolutely a grouping tool and sometimes that grouping is so we can export data and use it elsewhere. But VERY often data managers are using query as an data clean-up/audit/management tool and we use it to quickly identify, navigate to, and fix data entry issues.

I understand that the load burden in webview for loading large query results. I think at bare minimum, when the current limit is reached and we have an option to check a box to load the rest of the query for those circumstances when we need to work from within query.

To lose the functionality to use queries of any size to assist in data clean-up is a huge downgrade to RE and will increase the time it will take for us to perform critical data clean-up tasks, reducing efficiency.

Please course correct and enable us to load query results for queries of any size when necessary so that we can continue to perform our jobs efficiently.

We do our gift QC in Query so we can look at all gifts received in a week and scroll through to find errors. It's a critical part in the process to easily be able to click on the record to make any necessary changes. My most recent test of trying to do this in webview had 791 records with 30 columns and I got the error. I don't feel like this an obnoxious amount.

I have the same thoughts here. Exporting the data to view things isn't always a feasible workaround. I suggest (stolen from someone else on another idea who suggested this too) that there be a button at the bottom of the current row limit to load all the rest of the rows, and it could even have a warning about it taking a long time to do so if you'd like.

This is so important for database maintenance

This is a critical piece of functionality. Without the ability to view all records in a query directly in WebView, true adoption of WebView will continue to be slow. Query is an essential editing and data‑quality tool, and limiting visible results forces us back into Database View every time. Exporting isn’t a workaround — we need to open records, review data, and make updates in context.

Until all query results can be viewed and accessed in WebView, daily workflows take significantly longer and the transition away from Database View simply isn’t feasible

this is a critical need as database admins/managers transition to web view; the extra clicks and time needed to do our daily work in NXT is very cumbersome

Coming back here hoping to get more votes and a possible review! ! I just created what I considered a small query - 84 records, and was only able to view 36. Once again, I had to go to database view to complete my review of new students.

I literally just came to idea bank to see if someone had said this already. If I wanted an export, I'd export it! But what I want is to see all of my records and click into the ones I need to look at. And yes, sometimes, the number of records is huge!

Also, while I see the value in searching for a value and having the query show me records that meet that value, sometimes I still need to get to that place in a query. Having the option to do that is enormously helpful. Especially in large queries.

Presuming we are able to see all the records in the query.