Bug description
The search box on the table chart should show the total number of rows loaded. Now it shows search.num_records instead (see the screenshot).
Screenshots/recordings
Here is the screenshot from the 6.0 version:
For comparison, here's the same chart with the same data on 4.1.1 version:
Superset version
master / latest-dev
Python version
I don't know
Node version
I don't know
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Hi @saghatelian! I'm Dosu and I’m helping the superset team.
This is a confirmed regression in Superset 6.0.0: the table chart search box is showing the raw localization key search.num_records instead of the expected row count string. The root cause is a fragile translation workflow—plugin translations like search.num_records are registered only for the active locale at plugin load time, so if the locale changes or the plugin loads before the app's language is set, the translation may be missing and the key appears in the UI. This was likely made worse by recent refactoring in PR #34799, which changed how the table chart's search box and controls are rendered.
For now, there isn't a documented workaround. If you need a temporary fix, you could try ensuring your Superset instance is set to the desired locale before loading the table chart, but this may not be reliable. The best next step is to monitor for updates or fixes related to plugin translation registration and locale handling in future releases. If you have custom locale settings, double-check that they're applied before the table chart plugin loads.
Relevant code and technical details:
- Table chart search box uses tn('search.num_records', count) for its placeholder, expecting a translated string like "706 records" source.
- The translation key is defined in the plugin's i18n.ts, but may not be registered for all locales at runtime.
Let me know if you need more technical details or want to discuss possible workarounds.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: cbum-dev
Hi @msyavuz can I work on this issue?