Summary
Improve the dataset detail experience by:
- supporting export of selected rows only
- fixing intermittent dataset refresh/load failures on owned datasets
Problems
1. Export currently ignores row selection
The dataset table already supports row selection via checkboxes, but:
currently export the entire dataset instead of only selected rows.
Users should be able to:
- select specific rows
- export only those rows
- preserve column headers/attribute names in the exported file
2. Intermittent "Dataset not found" runtime error
Refreshing owned dataset pages sometimes throws:
Dataset not found
- Convex query runtime error
- Next.js runtime overlay
But clicking "Retry" successfully loads the dataset afterward.
This suggests a race/timing/hydration/query consistency issue in the dataset page loading flow.
The current UX is confusing because:
- the dataset actually exists
- retry succeeds
- but the initial render fails noisily
Scope
Selected-row export support
Implement selected-row-only export behavior for:
Requirements:
- if rows are selected → export only selected rows
- if no rows selected → preserve current full-export behavior
- exported files must include column/attribute names
- preserve current export UX/buttons where possible
- maintain clean behavior in dark/light mode
Dataset refresh reliability
Investigate and fix the intermittent:
Dataset not found
- Convex query hydration/runtime issue
Focus on:
- query timing
- initial render behavior
- transient loading states
- retry consistency
- route/data synchronization
- useQuery lifecycle behavior
The page should:
- fail gracefully
- avoid noisy runtime overlays for recoverable states
- handle temporary unavailable/loading states correctly
Deliverables
- selected-row CSV export
- selected-row XLSX export
- reliable dataset refresh behavior
- cleaner loading/error handling
- preserved table selection UX
Summary
Improve the dataset detail experience by:
Problems
1. Export currently ignores row selection
The dataset table already supports row selection via checkboxes, but:
currently export the entire dataset instead of only selected rows.
Users should be able to:
2. Intermittent "Dataset not found" runtime error
Refreshing owned dataset pages sometimes throws:
Dataset not foundBut clicking "Retry" successfully loads the dataset afterward.
This suggests a race/timing/hydration/query consistency issue in the dataset page loading flow.
The current UX is confusing because:
Scope
Selected-row export support
Implement selected-row-only export behavior for:
Requirements:
Dataset refresh reliability
Investigate and fix the intermittent:
Dataset not foundFocus on:
The page should:
Deliverables