If the task will only make sense to a dev, add a :zap: to the title.
Currently the actions for storing Recordsets on devices are in the Recordset rows (on /Records), and not the actual Recordset data.
This causes users to enter the row, set their filters, back out and then cache results.
We can take these actions and add them to the Recordset entries, to avoid needless back and forth
Value Add
Ease of use
Intuitive
Acceptance Criteria
[ ] In the recordset, allow a user to perform C~R~UD Operations on their Caches
Describe the task
Currently the actions for storing Recordsets on devices are in the Recordset rows (on
/Records), and not the actual Recordset data. This causes users to enter the row, set their filters, back out and then cache results.We can take these actions and add them to the Recordset entries, to avoid needless back and forth
Value Add
Acceptance Criteria
Additional Context
-