pass a parameter to controller of partial view

Question

I have an asp.net mvc View Report.cshtml that is a report and displays info from many classes. For most of the report I put info into arrays then do loops on the page to get the values from the arrays. There are two sections that I thought I would try to use partial views on because each one loops 16 times and each section has similar layout but different info. I need to pass a parameter so that I can call a method to get the data for each iteration. I tried to use partial views and pass the value of the parameter to the view by using

var model = new Competency 	
{ 		Dimension = i 	}; 	
@Html.Partial("CompPage",model)

This never hits the controller so it always comes back empty.

Then I tried Html.Action

@Html.Action("CompPage", "CareerCompetency", new { Dimension = i, HideScores, CompStanine = CompStanine[i], NarrativeIcon = NarrativeIcon[i] })

and also Html.RenderAction.

{Html.RenderAction("CompPage", "CareerCompetency", new { Dimension = i, HideScores, CompStanine = CompStanine[i], NarrativeIcon = NarrativeIcon[i] });}

While I can see the value being passed to the controller with both Html.Action and Html.RenderAction, it comes back as 404 when it tries to display the parent view.

Is there a way to do this with partial views or do I just go back to getting the info on calling controller and putting into arrays?

Here is the PartialView CompPage

@model VHRC.Models.Competency
@{
	bool HideScores = (bool)ViewData["HideScores"];
	string Stanine = ViewData["CompStanine"].ToString();
	string NarrativeIcon = ViewData["NarrativeIcon"].ToString();
}
		
			
				
					@Html.DisplayFor(model => model.CompetencyText)
				
			
		
		
			
				
			
			
				@Html.DisplayFor(model => Model.Narrative)
			
		
		
			Key Behaviors
			
				
				@foreach (var behavior in Model.Behaviors)
				{
					@Html.Raw(behavior.BehaviorHeading)
						
						@foreach (var item in behavior.BehaviorItem)
						{
							@Html.Raw(item.BehaviorText)
						}
						
					
				}
				
			
			
			@if (!HideScores)
			{
					 
				
 
			}

Here is the controller for that (after I tried using Action and RenderAction)

public PartialViewResult CompPage(int? Dimension, bool HideScores, int CompStanine, string NarrativeIcon)
        {
            try
            {
                Competency comp = new Competency();
                if (Dimension == null)
                {
                    return null;
                }
                Competency model = comp.GetCompetency((int)Dimension);
                ViewData["CompStanine"] = CompStanine;
                ViewData["NarrativeIcon"] = NarrativeIcon;
                ViewData["HideScores"] = HideScores;
                return PartialView(model);
            }
            catch (Exception ex)
            {
                Errors.ErrorOccured(ex);
            }
            return null;
        }

Accepted Answer

The code looks like MVC ASP.NET Framework. In MVC 2+ The child action solves this problem.

https://haacked.com/archive/2009/11/18/aspnetmvc2-render-action.aspx/

Answer

Issue: You're trying to use partial views in your ASP.NET MVC Report.cshtml to handle repetitive sections. While using Html.Partial doesn't invoke the controller (resulting in empty data), Html.Action leads to a 404 error.

Solution: Use Html.Partial by preparing all necessary data in your main view's model. This approach avoids extra controller calls and prevents the 404 error.

Steps:

Update Your ViewModel:

Create a main ReportViewModel that includes all data needed for the partial views.

public class ReportViewModel
{
    public bool HideScores { get; set; }
    public List CompStanine { get; set; }
    public List NarrativeIcon { get; set; }
    public List Competencies { get; set; }
}

public class CompetencyPartialViewModel
{
    public Competency Competency { get; set; }
    public int CompStanine { get; set; }
    public string NarrativeIcon { get; set; }
    public bool HideScores { get; set; }
}

Populate ViewModel in Controller:

In your controller action, populate the ReportViewModel with all necessary data.

public ActionResult Report()
{
    var model = new ReportViewModel
    {
        HideScores = /* your logic */,
        CompStanine = /* populate list */,
        NarrativeIcon = /* populate list */,
        Competencies = new List()
    };

    for (int i = 0; i < 16; i++)
    {
        var competency = Competency.GetCompetency(i);
        model.Competencies.Add(new CompetencyPartialViewModel
        {
            Competency = competency,
            CompStanine = model.CompStanine[i],
            NarrativeIcon = model.NarrativeIcon[i],
            HideScores = model.HideScores
        });
    }

    return View(model);
}

Use Html.Partial in Your Main View (Report.cshtml):

Loop through the Competencies and render the partial view with the prepared data.

@model YourNamespace.ViewModels.ReportViewModel

@foreach (var comp in Model.Competencies)
{
    @Html.Partial("CompPage", comp)
}

Update Partial View (CompPage.cshtml):

Modify the partial view to use the CompetencyPartialViewModel.

@model YourNamespace.ViewModels.CompetencyPartialViewModel


    
        
            @Html.DisplayFor(m => m.Competency.CompetencyText)
        
    


    
        
    
    
        @Html.DisplayFor(m => m.Competency.Narrative)
    


    Key Behaviors
    
        
            @foreach (var behavior in Model.Competency.Behaviors)
            {
                
                    @Html.Raw(behavior.BehaviorHeading)
                    
                        @foreach (var item in behavior.BehaviorItem)
                        {
                            @Html.Raw(item.BehaviorText)
                        }
                    
                
            }
        
    
    
        @if (!Model.HideScores)
        {
            
        }

Benefits of Using Html.Partial:

Performance: Avoids multiple controller calls, enhancing load times.
Simplicity: Centralizes data preparation, making the code easier to manage.
Avoids Routing Issues: Eliminates 404 errors related to incorrect controller/action routing.

Alternative (If Controller Logic Is Needed): Ensure your CareerCompetencyController and CompPage action are correctly named and accessible.

public class CareerCompetencyController : Controller
{
    public PartialViewResult CompPage(int Dimension, bool HideScores, int CompStanine, string NarrativeIcon)
    {
        var model = Competency.GetCompetency(Dimension);
        ViewData["CompStanine"] = CompStanine;
        ViewData["NarrativeIcon"] = NarrativeIcon;
        ViewData["HideScores"] = HideScores;
        return PartialView(model);
    }
}

Check:
- Controller name ends with Controller.
- Partial view CompPage.cshtml is in Views/CareerCompetency/ or Views/Shared/.
- Correct routing is configured.

Conclusion: Using Html.Partial with a well-structured view model is the most efficient way to render partial views without encountering controller-related issues. This approach ensures better performance and easier maintenance.Issue:

You're trying to use partial views in your ASP.NET MVC Report.cshtml to handle repetitive sections. While using Html.Partial doesn't invoke the controller (resulting in empty data), Html.Action leads to a 404 error.

Solution:
Use Html.Partial by preparing all necessary data in your main view's model. This approach avoids extra controller calls and prevents the 404 error.