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
Looking for a workaround for New Row in SQL Server
Best answer by SamB
Hi there
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. 🙏
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.


