Skip to main content

Hi folks, first time here. Greetings.

I’m struggling with Tables. I have a form on an interface page, page Q1. When I use a zap to update a record on form submission, it creates a new record and leaves the original record in the table. Instead I just want it to update the record, not duplicate it.

Here’s the table showing a duplicate entry instead of just updating column Q1 to true:

Here’s the Zap:

 

I’d be utterly grateful if someone could explain to me how to avoid the duplicate record in the Table!

Thanks in advance.

Hi @James C 

Check your Zap Runs history to see the DATA IN/OUT for each Zap Run to help you troubleshoot why duplicates are happening: https://zapier.com/app/history/


Thanks @Troy Tessalone , I went ahead and checked that.
Data in/out are fine with and it all goes through ok with status 200’s for GET, GET, PATCH.

I just looks like zaps to “Update Record” actually mean “Create New Record”  leaving the existing record in the Table - why on earth I don’t know! Seems bonkers to have additional rows in a table for each new update to a record, rather than updated the record all on one row.

 

 

Data In

table_id:

01HQ6865V3EB3RRHDZWTH1V8YY

record_id:

01HQBBN7P20A3ZV76KAPY7HVJY

new__data__f13:

True

zap_id:

228110104

zap_step_id:

228110105

zap_path_run_id:

006299f6-8aee-aacc-96bf-6abb7e22c491

 

Data Out:

new:

data:f1:

y@l.com

f2:

null

f3:

null

f4:

 

f5:

true

f13:

True

f14:

null

f15:

null

f16:

null

id:

01HQBBN7P20A3ZV76KAPY7HVJY

edited_at:

2024-02-23T16:09:35.071841+00:00

created_at:

2024-02-23T16:09:31.074000+00:00

schema_revision_id:

25

errors:

old:

data:f1:

y@l.com

f2:

null

f3:

null

f4:

 

f5:

true

f13:

 

f14:

null

f15:

null

f16:

null

id:

01HQBBN7P20A3ZV76KAPY7HVJY

edited_at:

2024-02-23T16:09:31.073719+00:00

created_at:

2024-02-23T16:09:31.074000+00:00

schema_revision_id:

25

errors:

record_id:

01HQBBN7P20A3ZV76KAPY7HVJY

table_id:

01HQ6865V3EB3RRHDZWTH1V8YY

change_id:

01HQBBNBP81TNMZQKH5NEMT7J2

 

Logs output:

{ "data": s { "change_id": "01HQBBNBP81TNMZQKH5NEMT7J2", "old": { "data": { "f1": "y@l.com", "f2": null, "f3": null, "f4": "", "f5": true, "f13": "", "f14": null, "f15": null, "f16": null }, "id": "01HQBBN7P20A3ZV76KAPY7HVJY", "edited_at": "2024-02-23T16:09:31.073719+00:00", "created_at": "2024-02-23T16:09:31.074000+00:00", "schema_revision_id": 25, "errors": {} }, "new": { "data": { "f1": "y@l.com", "f2": null, "f3": null, "f4": "", "f5": true, "f13": "True", "f14": null, "f15": null, "f16": null }, "id": "01HQBBN7P20A3ZV76KAPY7HVJY", "edited_at": "2024-02-23T16:09:35.071841+00:00", "created_at": "2024-02-23T16:09:31.074000+00:00", "schema_revision_id": 25, "errors": {} }, "record_id": "01HQBBN7P20A3ZV76KAPY7HVJY" } ], "events": { "planned": ], "suppressed": n] }, "meta": null }


@James C 

If you suspect an issue, you can try opening a ticket with the Zapier Tables Team: https://eap.zapier.app


@Troy Tessalone Will do, thanks very much for your time and input 👏