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.

Best answer

Cannot convert from Unicode 120120 to SQLWCHAR. Value is too large.

  • July 17, 2020
  • 6 replies
  • 387 views
G

I am trying to pass information from facebook leads to SQL Server and it generates this error

 

The row could not be sent to SQL Server.

Cannot convert from Unicode 120120 to SQLWCHAR. Value is too large.

 

I have tried switching to all the different data types that SQL Server allows but none works

helpme please

Best answer by SamB

Hey folks, just reaching out here to share that the bug has been fixed! 🎉

Thanks so much for everyone’s patience on this. In case you missed the email notification that went out here’s the main details from it:

“We’ve fixed an issue in the latest version where certain Unicode characters—including emojis—were not being handled correctly. This should now work as expected.

As a reminder, for the best results when working with emojis or special characters, we recommend using nvarchar column types. SQL Server does not reliably support Unicode characters in types like varchar.”

That said, if you continue to run into errors when using emojis or special characters, feel free to start a new topic or reach out to our Support team directly and we’ll be happy to assist.

In the meantime, happy Zapping! ⚡

    This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

    6 replies

    AndrewJDavison
    Forum|alt.badge.img+11
    • AndrewJDavisonZapier Solution Partner
    • Zapier Solution Partner
    • July 17, 2020

    @GUPTY 

    I'm going to flag this post for the Zapier Community Team. They should have more insight on this and can escalate to the support team if needed.

    Sit tight, and someone will contact you soon.

    Find out more and hire me: https://zapier.com/partnerdirectory/andrewjdavison (andrew@andrewjdavison.com)
      Liz_Roberts
      Forum|alt.badge.img+8
      • Liz_RobertsZapier Staff
      • Zapier Staff
      • July 17, 2020

      Thanks Andrew!

      Hi @GUPTY , I see you have been working with Support on this and appear to be affected by an open issue with special characters causing an issue in SQL Server.

      You have been added to a report about this so that the app's technical team can look at it. This does the following:
       

      • Re-raises this issue with the app’s team
      • Adds weight to the issue in queue
      • Reminds us to update you once this is resolved


      Once there is an update, you'll definitely be notified! In the meantime, please let us know if you have any additional questions!

       

      G
      • GUPTYBeginner
      • Author
      • Beginner
      • July 17, 2020
      @Liz_Roberts  @AndrewJDavison_Luhhu  
      Perfect, I hope I know of a quick solution that my client urgently requires.

       

      Thank you
        
      A

      Hi I have the same issue. It Happen when a lead contain special chars like  hearts or smiles.

      Can I manage the issue from the zap directly or I have to set some different options to my table in sql server ?

      Liz_Roberts
      Forum|alt.badge.img+8
      • Liz_RobertsZapier Staff
      • Zapier Staff
      • September 15, 2020

      Hi @AdminServiceEvolution ,

      I see you are working with Support on your specific configuration. I will let them continue to troubleshoot but please let us know what resolution you reach! 

      SamB
      Community Manager
      Forum|alt.badge.img+11
      • SamBCommunity Manager
      • Community Manager
      • Answer
      • April 1, 2025

      Hey folks, just reaching out here to share that the bug has been fixed! 🎉

      Thanks so much for everyone’s patience on this. In case you missed the email notification that went out here’s the main details from it:

      “We’ve fixed an issue in the latest version where certain Unicode characters—including emojis—were not being handled correctly. This should now work as expected.

      As a reminder, for the best results when working with emojis or special characters, we recommend using nvarchar column types. SQL Server does not reliably support Unicode characters in types like varchar.”

      That said, if you continue to run into errors when using emojis or special characters, feel free to start a new topic or reach out to our Support team directly and we’ll be happy to assist.

      In the meantime, happy Zapping! ⚡

      Terms & ConditionsAccessibility statement