Summary:
In ERPNext version 15 and above, the eye icon on number cards (used to show/hide cards on the dashboard) is not functioning as expected. This was working perfectly in ERPNext version 14, but after upgrading to v15 or newer, the functionality appears broken or unresponsive for end-users.
Use Case:
In the dashboard view, each number card (KPI card) includes an eye icon which allows a user to hide or unhide that card for their personal view. This helps in customizing dashboards without globally affecting other users. It’s particularly useful when users want to focus only on selected metrics relevant to them.
Issue Description:
After upgrading from ERPNext v14 to v15 (and verified on v15.10+), we observed that:
*Clicking the Customize Dashboard option in Dashboard settings(3 dots at right corner).
- Clicking the eye icon (
) does not hide the card anymore. - The UI doesn’t reflect any change, and the card remains visible.
- No errors are thrown in the browser console, making it harder to trace the failure.
- It only impacts user-specific visibility settings; global deletion or creation of cards still works.
In contrast, this feature was working smoothly in ERPNext v14 — clicking the icon would hide the number card immediately, and it would remain hidden across sessions for that user.
Steps to Reproduce:
- Go to any dashboard (e.g., Stock, Sales, CRM, etc.).
2.Clicking the Customize Dashboard option in Dashboard settings(3 dots at right corner). - Click on the eye icon on any number card.
- Observe that the card does not hide or reflect any state change.
Expected Behavior:
- Clicking the eye icon should toggle visibility of the number card for that specific user.
- The setting should persist across sessions.
- The UI should immediately reflect this change (i.e., hide the card).
Environment:
- ERPNext Version: 15.x (Tested on 15.10.x and above)
- Frappe Framework: Corresponding 15.x version
- Browser: All modern browsers tested (Chrome, Firefox)
Additional Notes:
- It appears this may be a regression bug introduced in v15.
- This issue may be related to changes in how user-specific dashboard configurations are stored or updated in v15+.
- We tested on a clean v15 site and the issue persists, so it’s unlikely to be a custom code conflict.
,
Temporary Workaround:
Currently, there’s no frontend fix unless you manually modify the dashboard settings via backend or DB — which is not user-friendly.
Request:
- Can the core team or community confirm this behavior?
- If it’s reproducible, can it be logged officially as a bug?
- Any guidance on a temporary patch or custom workaround would be appreciated.
Thanks in advance for the support!
— Ann Riya Jaison | Faircode Next Private Limited
