Apache Superset Include specific counts of data affected during create, update or delete operations instead of generic messages as follows

Bug description

Include specific counts of data affected during create, update or delete operations instead of generic messages as follows

using superset in k8s version Version: 4.1.2

please let me know if this can be fixed in superset config level

Screenshots/recordings

Superset version

master / latest-dev

Python version

3.9

Node version

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]

Superset does not currently offer a configuration option to display specific counts of affected rows in feedback messages for create, update, or delete operations. These messages are hardcoded in the backend (Python/Flask) and frontend (React/JS) and typically do not include row counts—just generic success or error text. For example, delete operations show messages like "Deleted: [item name]" rather than the number of rows affected.

There was a recent improvement for dataset column operations that now shows the number of columns added, modified, or removed, but this is limited to dataset schema changes and does not apply to general CRUD operations on data (example PR).

To display affected row counts for general data operations, code changes would be needed in both the backend (to expose the counts) and the frontend (to display them in messages) reference. There is no way to achieve this via Superset configuration alone.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

Comment From: sandy4597niko

so that means in 4.1.2 i can't add this feature ?

Comment From: rusackas

In this setting I would assume "the query returned no data" means there are 0 rows returned. Something is busted.

Are there any reproduction steps you can give us so that we can encounter the error and help troubleshoot?

Are you experiencing this in newer (4.1.3/5.0.0) versions as well?