glideapps / glideapps/expert-issues
Native Server-Side Search, Filter, and Sort in Data Editor for Big Tables
- Dominant language
- No language data
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
**Summary**
Developers need standard data management tools—**Search, Filtering, and Sorting**—directly within the **Data Editor** interface.
Currently, navigating Glide Big Tables (25,000+ rows) relies entirely on "Lazy Loading" (pagination), where rows load in chunks (e.g., 1,000 at a time) as the scrolls. This makes finding specific records or viewing the most recent data cumbersome, as browser-based search (`Ctrl+F`) does not work on data that hasn't been loaded into the DOM yet.
**Current Problem**
1. **Cannot Find Specific Rows:** To find a specific `Row ID` or value located deep in the table (e.g., row 20,000), the developer must manually scroll down repeatedly to trigger the loader multiple times until the data appears.
2. **Sorting Issues (Accessing New Data):** New rows are appended to the bottom. To check the most recent entries (e.g., debugging a new submission), the developer is forced to scroll through the entire history of older records just to reach the bottom. We need a **"Sort Descending"** feature to flip the view and see the newest rows at the top instantly.
3. **Lack of Filtering:** There is no way to isolate a subset of data (e.g., "Show only rows where Status = Error"). Developers have to visually scan the full list, which is inefficient and prone to missed details.
**Examples/Scenarios**
* **Data Correction:** A user reports an issue with a specific transaction. The developer knows the ID, but the record is somewhere in the middle of 25,000 rows. Without a Search function, they have to "guess" where to scroll or keep scrolling until it loads.
* **Monitoring:** A developer wants to quickly see the last 10 rows added to the table to verify a workflow. Currently, they must scroll past 24,990 old rows to get there.
**Suggested UX**
* **Server-Side Search:** A search bar that queries the backend database directly (finding rows even if they aren't currently loaded in the view) and jumps to the result.
* **Column Headers:** Right-click context menu on headers to:
* **Sort:** Ascending / Descending.
* **Filter:** Simple conditions (Equals, Contains, Empty).
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.