How to Create Two Independent Submit Buttons for Different Actions in ASP.NET Core

Learn how to effectively manage two different submit buttons in ASP.NET Core that save data to two separate databases on a single view.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Two different buttons that save to two different databases in one view. ASP.NET Core

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Managing Multiple Submit Buttons in ASP.NET Core

In web development, especially when using frameworks like ASP.NET Core, one common requirement is to have a single view that can handle actions for two different buttons. This can be very useful when you want to save data to two distinct databases with minimal user interaction. In this guide, we will explore a specific problem where two buttons in an ASP.NET Core form do not behave as expected and provide a detailed solution.

The Problem

The issue arises when the first button, submit, functions correctly by calling AddOrEdit in the controller and saving the data to the database. However, when you click the second button, submit2, which is supposed to trigger the SubmitDB action, the same AddOrEdit action gets called instead.

Here's a quick overview of how the buttons are laid out:

Button 1: id="submit" - correctly triggers AddOrEdit

Button 2: id="submit2" - intended to invoke SubmitDB but fails to do so

Here’s a quick snippet of the relevant HTML code:

[[See Video to Reveal this Text or Code Snippet]]

The Solution: Use JavaScript for Better Control

To properly handle this situation, we can utilize JavaScript to specify which action should be called when each button is clicked. This will involve adjusting the button HTML and adding a JavaScript function to dynamically set the form's action attribute before submission.

Step-by-Step Implementation

Modify Button HTML: Adjust your buttons to call a JavaScript function that can dynamically assign the action based on the button clicked.

[[See Video to Reveal this Text or Code Snippet]]

Create a JavaScript Function: Include a JavaScript function that sets the form's action attribute based on the button clicked.

[[See Video to Reveal this Text or Code Snippet]]

Form Tag: Ensure your form has an ID so that the JavaScript can reference it correctly.

[[See Video to Reveal this Text or Code Snippet]]

Example Implementation in Code

Here’s a quick consolidated version that puts everything together:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By following these steps, you can effectively manage two different submit buttons in an ASP.NET Core view that trigger different actions. This reduces user friction while ensuring that the correct data is saved to the appropriate databases. Implementing JavaScript for dynamic form submission is not only efficient but also a best practice when dealing with multiple actions in a single view.

For more insights into ASP.NET Core development, keep exploring our blog!