Hi have a scenario where in i have 3 views in the first view i have some textbox and then next button on click of next button the second view will be shown and the second view will also have some textbox and next button the third view is the final view which has few textboxes and submit/finish button. On click of submit/finish button all the data from view1,view2 and view3 should be saved to database. How to achieved it using ASP.NET MVC
You can use temp-data and their keep method to persist data in subsequent request.
Just keep all required field data into temp-data and get all this in one object(temp-data) and save them
Here is an eg. for it:
public ActionResult Add(Model model)
{
if(ModelState.IsValid)
{
db.Model.Add(model);
db.SaveChanges();
return RedirectToAction("Add2");
}
return View(model);
}
it redirects to the second view or a partial view, and the same with the 2nd to the 3rd. Hope it helps.
if you want to pass data from one view to another view then you can use TempData
ex.
TempData["Key"] = "test";
and can get value from tempdata like
#{
var abc = TempData["Key"];
}
Note: You can get tempdata value to next action after that it will be destroy.
Related
I'm using Xcode Swift 3.0, I have 5 view controllers, each controller have several textField. Once the information finish filled, press nextButton to next view controller. For example, finish fill in all textField in view controller 1, click nextButton and I will segue it to view controller 2, and so on.....
I want to get view controller 1,2,3,4 entered textField information only from view controller 5.
How am I gonna to do that without using Segue to pass data from vc1 to vc2, and from vc2 to vc3 and so on?
Please advice.
TempData can be used for passing value from Controller to View and also from Controller to Controller.
Find the example:
public class FirstController : Controller
{
// GET: First
public ActionResult Index()
{
TempData["Message"] = "Hello MVC!";
return new RedirectResult(#"~\Second\");
}
}
public class SecondController : Controller
{
// GET: Second
public ActionResult Index()
{
return View();
}
}
How am I gonna to do that without using Segue to pass data from vc1 to vc2, and from vc2 to vc3 and so on?
No matter whether you're using Swift or Objective-C, the right solution here is to use a data model. Each view controller gets a reference to a common data model from the object that creates it, and the view controller uses the model to populate its views. The view controller updates the model as the user makes changes. Since the other view controllers also refer to the same model, they all automatically get the user's changes.
This is one of method inside my controller.
[HttpPost]
public JsonResult Ajax(string AJAXParameter1)
{
List<string> data = new List<string>();
data.Add("AJAXParameter1=" + AJAXParameter1);
return Json(new { data, result = "OK" });
}
If parameter AJAXParameter1 recieves value as passport i want to display view that contains fileds related to passport. If it recieves value as pan i want to render some different view that allow us to add pan card related details. For pan and passport i have models. Based on Id i want to generate view.
I believe the best way to do this is to simply create two views or partialviews based on how your application will have to look, one for the passport and one for the pan card.
Then in your controller method see which one you receive and return the view needed.
something like:
[HttpPost] public ActionResult ReturnNeeded(string Parameter1){
if (IsPassport(Parameter1)){
return View("PasswordView");
}else if (IsPan(Parameter1)){
return View("PanView");
}
return View("OopsBadRequest");
}
maybe?
Session variable lost after a controller calls another View to render.
public ActionResult Index(Customer model, string cancel, string effective)
{
if(!string.IsNullOrEmpty(cancel))
{
//update database
Session["variable2"] = new Info(){ Text = "Do not processed"};
return View("Cancelation"); //error stated occurs when calling another view
}
if(!string.IsNullOrEmpty(effective)
{
//do data base update
Session["variable1"] = new Info(){ Text = "Processed"};
return View(model); //All good here
}
{
I have a MVC controller that when post back to it I set a Session variable "variable1", then I do return View(model). In this case all is good I can access the new Session variable1 everywhere.
But when I post back to the same controller again, I check the button clicked and then I set another Session variable, "variable2" this time I do return View("Cancelation").
This last variable2 is lost and does not show on HttpContext.Current.Session["variable2"] anywhere in the application.
Can someone help to understand why?
What I found was that because I was using SQL Server as Session store, I had to use Serialize() attribute on the object, then it worked.
When I click on Edit button in my Index page, just to get some other control values also am calling the HttpPost method, by using the Edit button as Submit button. So here is my controller method,
[HttpPost]
public ActionResult Edit(Employee emp, IEnumerable<string> Check, int empId = 0)
{
emp = new Employee(empId);
// some action with `Check` values
return View(emp);
}
If I call my edit view like this, some of the values are binding in the corresponding EditFor, and some of them are not.
If I dont call HttpPost method, and just pass the Id using Html.ActionLink all the values are being displayed properly in my Edit view.
I am struggling with this for a long time. Can anyone help me out here?, thanks in advance.
Say the requirement is to redirect to another page after successfully saving a model in an ASP.NET MVC controller:
[HttpPost]
public ActionResult Index(ViewModel viewModel)
{
if (ModelState.IsValid)
{
// Do save;
return RedirectToAction("whatever"); // <--- here's the problem
}
// display validation errors and so
return View(viewModel);
}
This would work fine unless the controller was rendered as a Child Action:
#{
Layout = "my layout";
Html.RenderAction("something else, a view for example");
Html.RenderAction("Index action of the above controller"); // <----
}
In this case RedirectResult class would check and see that the context is a child action and would throw the exception: "Child actions are not allowed to perform redirect actions".
I understand that writing to Response stream is already in progress and a redirect cannot take place here but nevertheless one has to be able to redirect to other pages after a server-side action in a controller even if that action is a child action. We use Layouts and RenderActions to reuse the shared parts of the page design.
How would you implement such a redirect in such a controller?
Edit:
The main goal is to reuse View/Controllers that do a specific job and split them to logical concepts like displaying some data or providing an edit form. My approach here is to use RenderAction to render their result into a container. Container view (main page's Index action) acts as a traditional asp.net Page, its Layout view as a Master page and edit and view controller/views are equivalent to User Controls (modules). The problem is there is no way to Redirect the Response after something has been written to it:
I'll submit a new answer in an attempt to keep things clean.
A normal mvc flow goes like this :
Http command reaches 1 controller which acts as a choirmaster(aka controller) and calls several logic containers(e.g services / commandHandlers) :
public ActionResult Index(){
var data = _yourService.FetchData();
return View(data);
}
This controller renders 1 view which can have multiple partials
#{
Layout = "my layout";
}
<p>Some html</p>
Html.RenderPartial("A shared partial");
Html.RenderPartial("shared\yourUserControl", Model.PropertyOrSomething);
If the partial contains too much logic to generate you could add a RenderAction or create an htmlHelper extension.
But neither of these should be able to control the flow of your request, a save or something that can redirect should in my opinion never be called from inside a view.
I assume you want to reuse the code in your controller so badly because it is getting quite big.
My advice would be to try and clear that controller up as much as possible by delegating as much of the logic upwards as you can.
Just by looking at your controller method for 5 seconds you should get an idea of what this action will do, if that's not the case : refactor it ! :)
If i understand correctly you have a parent controller which accepts a saveAction and while rendering the view you call another(?) saveAction as a child.
This flow feels unnatural to me. The parent action and only the parent action should handle the save command. You can render as many child actions as you want as long as they are only used to render some html(as this is what the view does). Don't let them handle redirection or saving, that way of working is everything but transparant for colleges or future you.
The controller controls the flow, not the view.
Edit:
A normal setup would be having 2 actions, eg: Index and Put.
public ActionResult Index(){
//fill model with dropdown data etc
return View();
}
public ActionResult Put(viewModel data){
if (ModelState.IsValid)
{
// Do save;
return RedirectToAction("whatever"); // <--- here's the problem
}
// display validation errors and so
return View("Index",viewModel);
}
Edit2:
If you return View("Index",viewModel) you will generate your index view with it's layout and the validation messages will be located in the modelstate.
Your view however should only have 1 childaction(or more if there are multiple, as long as it's not the save action).
Your Index view could look like this :
#{
Layout = "my layout";
}
Html.RenderAction("something else, a view for example");
#Html.BeginForm("Put","YourController"){
//all your input controls which will also show the validation errors
}
Edit 3:
If you want to reuse html code you should use #Html.Partial or Html helper extension methods. Note that if you pass no model the parents model is passed but you can pass a submodel to match the type safety of the partial.
It would look something like this :
#{
Layout = "my layout";
}
Html.RenderAction("something else, a view for example");
Html.RenderPartial("shared\yourUserControl", Model.PropertyOrSomething);
Try using AJAX in your view to do this, and instead of returning a RedirectToAction in your controller, return a JSON object:
View:
$.ajax({
url: '<%: Html.ResolveUrl("~/ControllerFolder/ControllerName/") %>',
type: "POST",
data: data,
success: function (result) {
$("#Div").html(result);
if (result.redirectUrl != null)
{
window.location = result.redirectUrl;
}
}
});
Controller:
[HttpPost]
public ActionResult Index(ViewModel viewModel)
{
if (ModelState.IsValid)
{
// Do save;
return Json(new { redirectUrl = Url.Action("NewAction", "NewController", RouteValues)});
}
// display validation errors and so
return View(viewModel);
}
Hope this helps...