About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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.

Best answer

Failed to create a new row in MySQL: (pymysql.err.OperationalError) 1292 Incorrect date value

  • 21 September 2023
  • 5 replies
  • 212 views
M

Hi. I am attempting to extract a date from the email parser, format the date to the correct format YYYY-MM-DD an then insert the value into a mysql database. The format change looks correct, but the db add is failing because a timestamp is being added. Thanks in advance. 

 

My date/time format setup:

 

My date/time format output: 

 

My mysql data field map: 

 

The error I am getting from the mysql post: 

 

My mysql field setup: 

 

icon

Best answer by SamB 26 September 2023, 13:38

View original

5 replies

Troy Tessalone
Userlevel 7
Badge +14

@mrg 

The Cancel Request Date is a Date/Time format as indicated by the 2 icons next to the field label.

Looks like the value is being converted to a timestamp, when only a data is supplied.

That may be a backend config issue with the way the Zap app integration handles date field types.

 

You may need to open a ticket with Zapier Support: https://zapier.com/app/get-help

 

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
M

Thanks. This is definitely a problem with how Zapier is sending the data to the mysql database. It appears that since it is detecting that the data is a date, it is manipulating the structure into a datetime format before sending. I can confirm this because I have tried the following: 

  1. Formatting the data to change the structure to YYYY-MM-DD using the date/time format zap. 
  2. Formatting the data to change the structure to YYYY-MM-DD using the text format zap with a regex string.
  3. Removing all formatting from Zapier, changing the field type to VARCHAR, and passing the data as it was extracted from the email. 

In all cases, Zapier is restructuring the data in the full datetime format before sending. This is a bug as it is making a decision on behalf of the user that may not be desired. 

Troy Tessalone
Userlevel 7
Badge +14

@mrg 

You may need to open a ticket with Zapier Support: https://zapier.com/app/get-help

It appears there is an issue with the actual field type (date) vs the configured field type (date/time),

 

 

⚡ Troy Tessalone - AutomationAce.com | Premier Certified Zapier Expert | #1 Zapier Community Contributor
M

Just a follow-up here that support acknowledged that this is a bug. No word on a fix and I imagine it’s not a major issue so it’ll take awhile. 

SamB
Rank
Userlevel 7
Badge +11

Thanks so much for following up here, @mrg.

I’m so sorry that you’re running into a known issue with the MySQL app. There’s no updates on the bug that I can share at the moment and I can’t make any promises around when it might be solved by but we’ll definitely be in touch with you by email as soon as a fix is implemented.

I checked on the support ticket and it seems that you were able to workaround this issue by changing the field type from date to datetime. So thought it worth mentioning that workaround here in case it’s helpful to others running into this issue too. 🙂 

Reply


Terms & Conditions