Basic Actions - Unknown column "id"

Bug reports
1

I'm having enormous problems implementing Basic Actions on our MySQL database. I am running the latest version of Metabase. All of my models are straight SELECTs from the raw data, via the notebook editor with no filtering or custom columns.

1 - The UPDATE or DELETE actions from the object detail view give the error No destination parameter found for #{"id"}.

2 - Executing the CREATE action from either a dashboard or in the actions view gives the error Unknown column 'ID' in 'where clause'.

Both these errors are very strange - it appears as if you are assuming that every table has a Primary Key column called "ID"?

2

is the ID column mandatory on the table you want to insert to?

3

Was there a resolution to this?

4

I know its out of date, but this seem to happen when using basic actions + models in the “Upload” schema.

5

What’s the “Upload” schema?

6

Sorry I mean the upload database, see Setting up data uploads | Metabase Documentation

7

Basic actions require a single-column PK.

The upload models are special as they include a ID column PK (called _mb_row_id, on PostgreSQL at least) that’s automatically added as part of the upload process. Basic actions created on uploaded tables will use this PK. Note that actions on the upload db is not enabled by default, and should be enabled with care as refreshing the data in the backing table will destroy any changes performed through actions.

With respect to OP, It’s possible the table metadata is incorrect, the table definition was changed after creating the actions, or there was a bug in earlier times that didn’t attach this properly. At this stage it’s ancient history (and OP never came back to address the replies) so no telling what was going on there.

8

So what I found on my local testing is that if I enable Basic Action on top of a model thats using an “upload” table, I get No destination parameter found for #{"id"}. Found: ("_mb_row_id" "exclusion_date_start" "user") when I try to run the Update action on the details pane.

9

For completeness, what version of Metabase, and have you tried it on a freshly uploaded file?

I wasn’t able to reproduce this issue on 0.59.

10

Im on 0.59 as well.

I tested it on a fresh upload/model and got the same error.

TestUploadMetabase
TestUploadMetabase2514×1718 88.7 KB

"metabase-info": {

  "databases": \[

"h2",

"mysql"

  \],

"run-mode": "prod",

"plan-alias": "",

"version": {

"date": "2026-04-22",

"tag": "v0.59.8.2",

"hash": "9905305"

  },*...*
11

I wonder if it is a PostgreSQL vs MySQL thing. I’ll set up a test.

12

I was able to trigger the error message from the detail view when viewing the model’s table. Either Update or Delete actions will fail. Create is working fine from either the model edit panel or from a dashboard with a defined action button, so that seems to be an improvement over OP’s situation.

I checked that the _mb_row_id column is marked as an Entity Key in the metadata. Also can reproduce on both PostgreSQL and MySQL, so its not a database specific thing.

At this point its time for some code spelunking to see where the id column reference is coming from.

I’ll have to pick this up tomorrow.

13

I‘ve determined that only the Detail pane three-dots menu Actions fail when the Model has a Entity Key column not called id. Actions invoked from the definition page and dashboards work fine with such a model.

I have opened the following GitHub issue to get this problem fixed:

14

Thanks!