Hello team,
I would like to request an enhancement for full multi-language support in ERPNext, specifically for the Sidebar (Workspace sidebar) and Filter components.
Currently, many labels inside the sidebar and filters are taken directly from the database (Workspace and Filter JSON), which prevents them from being translated using the standard Translation system (_() function, CSV translations, or the Translation doctype). As a result, even when users switch their language (e.g., English ↔ Vietnamese), the sidebar and filters still display the original labels instead of translated ones.
Problems observed
-
Sidebar labels do not pass through the translation function.
-
Workspace items stored in the database cannot be translated dynamically.
-
Filter labels also ignore translations and always display the raw fieldname/label.
-
This affects the overall multi-language experience in ERPNext.
Why this is important
-
Many companies operate with multiple languages, especially across different regions.
-
Users expect the UI to change fully based on their selected language.
-
Sidebar and filters are core navigation elements — inconsistent translation decreases usability.
Requested Improvements
-
Ensure all sidebar labels are processed through the translation system (
_()ort()). -
Allow Workspace JSON labels to be translatable dynamically based on user language.
-
Add translation support for filter labels (field labels and filter option labels).
-
Provide a standard mechanism to override or translate workspace items without modifying the database structure.
Expected Outcome
-
Users switching languages will see the entire interface (including sidebar & filters) translated correctly.
-
Improved consistency with the rest of ERPNext’s multi-language features.
If possible, we hope the development team can review and include this improvement in an upcoming release.
Thank you!
