Record Selector Default Value Should Not Be First Record Of Table
A
Alex Pappas
I agree, in dashboards, the Record Selector widget currently auto-selects the first record from its source view. I’d like an option for the selector to remain unselected on load, or display a custom placeholder such as “Select a [Label]” (label customizable) or "Select an Option".
Why this matters
• Prevents accidental actions, particularly with new users, when a child widget (details, timers, approvals) reacts to an unintended default record.
• Reduces data errors in chained selectors (e.g., Parent → Child) where users should explicitly choose the child.
• Improves kiosk/shared-device flows where “last used” or “first in list” can point to the wrong record.
Suggested behavior/settings
• Default selection: None (require explicit choice), with an optional placeholder text field (e.g., “Select a [Bucket]”).
• Optional toggles:
• Auto-select only when a single result is returned.
• Show “Clear selection” button.
This keeps dashboards safer and clearer without breaking existing setups, while still allowing admins to opt into defaults when appropriate.
Jon Darbyshire
Great to hear your perspective, Santhan C! I have a few more questions for you:
- What specific scenarios or use cases are impacted by the current default selection behavior?
- Would you prefer the selector to display a custom message or remain unselected until a choice is made?
- Are there any specific conditions under which a default selection would be beneficial?