Skip to main content
Best answer

Looking for a workaround for New Row in SQL Server

  • February 23, 2026
  • 3 replies
  • 37 views

lamatekinc
Forum|alt.badge.img+1

A change to the SQL server connector has broken several of my zaps for SQL Server New Row as the final step. My tables are ERP tables and all have default insert/update and penultimate triggers. This step was working completely fine until this morning.

Now I’m receiving “The target table 'lam_external_lead' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.”

I understand what this error means, but I just don’t understand why Zapier started putting output parameters into this New Row step. It’s the last step of my zap so I don’t need the output to use in the next step, but there’s no option for this. 

Wonder if there is any workaround outside of a Custom Query?
Can I tell the zap somehow to not use output parameters, or is it possible to use a legacy version until I can create all the queries? Disabling triggers is not possible. 

 

Best answer by SamB

Hi there ​@lamatekinc 👋

I’m so sorry to hear about the disruption to your Zaps! I can see you also reached out to our Support team about this, and they added you to the bug report for this issue. Unfortunately we can't give any timelines on when it might be resolved, but we'll be sure to notify you by email as soon as it’s fixed.

Glad you were able to get a workaround in place, and thanks so much for taking the time to share details of it here. Really appreciate it, it'll definitely be helpful for others who run into the same issue. 🙏

3 replies

lamatekinc
Forum|alt.badge.img+1
  • Author
  • Tinkerer
  • February 24, 2026

I’m still finding it hard to believe Zapier made such a change with a major impact but after wrestling with my zaps and recreating them all day I came up with a very cumbersome but functional workaround if anyone else has this issue. 

You need the ability to create a view in your database.
1. Create a view with the exact same columns as your table and nothing else. You can exclude certain columns if you don’t need them
2. Add your SQL Server New Row step. Zapier won’t let you choose a view for this, so add your base table.
3. With all of the columns from the table present, change your table to the view name (helps if you just create the view something like table_vw) 
4. Refresh fields (not sure if this is necessary) and add the pills to your fields. 

While this is not ideal and I’m sure Zapier will break it, it’s preferred to a custom query where pilling all of the Values from the insert is a nightmare. 

another workaround would be a stored proc, but I think you’d run into the same issues with the custom query there. My fallback would be to create a separate table without triggers and then just call a stored proc with another step to insert into my desired table. What a mess. 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • Answer
  • February 24, 2026

Hi there ​@lamatekinc 👋

I’m so sorry to hear about the disruption to your Zaps! I can see you also reached out to our Support team about this, and they added you to the bug report for this issue. Unfortunately we can't give any timelines on when it might be resolved, but we'll be sure to notify you by email as soon as it’s fixed.

Glad you were able to get a workaround in place, and thanks so much for taking the time to share details of it here. Really appreciate it, it'll definitely be helpful for others who run into the same issue. 🙏


  • New
  • February 25, 2026

We have been affected by this and are still experiencing 1000 rows failing to Insert a day since it happened with NO resolution and no help from zapier. We have been passed around support with no acceptance that they screwed up!! Two weeks ago we found this issue with the premium connection and told them about it - we discovered that the old 1.2 connections worked fine and zapier told us they would not retire those so we were ok to Just continue using them. Then earlier this week overnight zapier upgraded all our zaps to premium and they all started failing and they removed the ability to publish a zap using the previous sql server connections they said would be on to continue using while they resolved the premium issues. We are still working on a workaround for our issue and will be getting off zapier as soon as we can after this experience.