I’ve seen a few hacks in the past to try and work out which button caused a form POST in ASP.NET MVC, but the truth is it is pretty easy.
Step 1: Inside your form, add two Submit buttons. Add a name attribute to both (note it isn’t added by MVC by default);
2: <input type="submit" name="Command" value="Save" />
3: <input type="submit" name="Command" value="Delete" />
Note both have the same name.
Step 2: Inside your action, add a parameter that matches the name of the buttons;
2: public ActionResult Index(
3: Person person,
4: string command)
6: bool saved = (command == "Save");
8: if (saved)
9: // code removed
11: // code removed
Simple huh? You could write some clever extension method to inspect the posted HTTP values, but I find this approach far more elegant. It is really clear that I’m expecting the “command” to be posted to my action.
A part of me wonders if naming all your buttons the same contravenes the HTML specification, but I can find no evidence of this – it is an accepted practice for checkboxes and radio buttons of course, and I’ve found this to work well. If you know otherwise do shout up. Like it? Hate it?
Step 3: Well… let’s take it one step further and create an enum of commands;
1: public enum Command
Step 4: … and update our action method parameter’s type to be our new enum, and of course our logic to use it;
4: Command command)
6: if (command == Command.Save)
7: // code removed
Hey presto! Strongly typed clear code that reacts to which button was clicked.
Original post by Simon Ince on 02-12-2011 here: http://blogs.msdn.com/b/simonince/archive/2011/02/12/detecting-which-button-was-clicked-in-mvc.aspx