Solving Microsoft SQL Server Module Update Issue

When working with the Microsoft SQL Server module in your scenario for updating the database, you might encounter a peculiar issue. After a successful update, the module might not return any bundles. This means there is no response, causing the scenario to stop and not execute any further modules in your flow.

What's the solution?

There are a couple of ways to tackle this issue. One way is to force MS SQL Server to return a response after an UPDATE. This can be done by using a query to update. After your update query, you can use the following:

IF @@ROWCOUNT > 0 PRINT ‘[{"afected_rows”: ‘+ @@ROWCOUNT+’}]’; ELSE PRINT ‘No rows’ GO

This will ensure that a response is returned after the update.

Another solution, and a simpler one at that, is to use a feature that might have been overlooked. There is a toggle "Continue the execution of the route even if the module returns no rows”. You simply just need to switch it on and even if there are no bundles after the update, the scenario goes further.

Troubleshooting Tips

If you're still encountering issues, make sure to double-check your update query and the settings of your SQL Server module. It's also a good idea to test your scenario with different settings to see what works best for your specific situation.

Conclusion

Working with databases and modules can sometimes be tricky, but with the right tools and knowledge, you can overcome any challenge. Remember, the key is to understand the problem, explore different solutions, and not be afraid to ask for help when needed.

You do have further questions?

Ask your question via E-Mail: Richard@make-app.de
Book a paid Support & Consulting Session
New Make.com user? Sign up through this Affiliate Link to receive 10.000 operations for FREE.