Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

This post was split from the topic: date.equals should be defined, instead was `undefined`


Hi all here we go again :)

Today I made some changes on the Gsheets source file and actually I see a success zap run, but no evidence on the Notion DB :(

Below is the screenshot where you can see “Data in” and “Data out” where the status has been change from “closing” to “Sold”.

But on Asset DB nothing I see a duplicated row with 2 different previous statuses. See ID QU36.

 

I also changed ID46 but it doesn’t appear on zap runs yet.

 

I also noticed other duplicated raws and it reflects the tests I made yesterday trying changing some value

 

Any help from there? :)

 

Thx folks

Hi @omarbortolato!

I hope you don’t mind but I’ve moved your question into a new topic since it seemed to be regarding a different issue with the same Zap.

It looks like the ID that’s been selected isn’t the actual ID for the database item in Notion, it’s a different reference number of some kind. Instead of a value like “QU36” I’d expect to see a long ID number containing a series of letters and numbers in the Item field. Like the ID shown here for example:

bfb6881dd1d8d53f5622d95d75d8817a.png

My guess here is that the Update Database Item action isn’t able to find a match for the number that’s been supplied so it’s creating a new one, which is where you’re seeing a duplicate item being created in Notion.

In order for the Zap to be able to update an existing item in Notion you’d want to add a Find Database Item search action to look for the item using the reference number supplied by Google Sheets (e.g. QU36). Then in the Item field (on the Update Database Item action), select the ID field from that search action (as pictured in the screenshot above). That should help to get the Zap to update the existing item in Notion correctly. 

Hope that helps. Please do keep us in the loop on how that goes!

Reply


Terms & Conditions