Can't access ViewBag in a partial view in ASP.NET MVC3

Question

I have a controller calling a view. In the view there is a PartialView called be @Html.Partial(\"ViewName\", model). This works fine.

But i

Answer 1

If you are using an overload of the Html.Partial() where viewData is one of the input parameters, for example:

@Html.Partial("PartialViewName", Model, new ViewDataDictionary(ViewBag))

then your partial view will not see data from your original ViewBag.

Remove new ViewDataDictionary(ViewBag), so you should write

@Html.Partial("PartialViewName", Model)

Answer 2

In a comment TehOne said:

I know this is a bit old, but for future reference, I solved this by using ViewContext.Controller.ViewBag.Property. Of course this means that the ViewBag property you are trying to access was set in the controller, but I think that is a common enough case.

Which is what worked for me.

Answer 3

My senario was, I had partial view with Model IEnumerable<SampleModel> However I had to pass using, coz Model.SampleModelList can be null

@Html.Partial("PartialViewName", Model.SampleModelList, new ViewDataDictionary())

The simple solution was since PartialView is also now part of View every element on View can be accessed by PartialView so I did set the ViewBag data to data-element on View html, instead of ViewBag.

<div class="showcase-heading" id="dvValue" data-id="@Model.ContentId">@Model.Name</div>

Answer 4

I was having this same problem with a very basic page:

@Html.Partial("_AppIntro")

<div class="form-group row">
    <div class="col-md-10">
        <a href="/Ag/Application/1" class="btn btn-default btn-primary">Next</a>
    </div>
</div>

And the partial view contained only text with some references to ViewBag to fetch some dynamic values passed from the controller. It turned out that the name of the partial view mattered. Removing the partial page and recreating it with Add -> View -> MVC 5 View but naming the page _AppIntro.cshtml fixed it.

Answer 5

> In a general scenario, when you use Html.Partial;

Html.Partial("partialViewName");

The Model that is sent for parentView, can be used for in the partialViewName. Moreover, the ViewData which is send for parentView can also be used for partialViewName.

> As a special case, when you use Html.Partial and if you want to send Model..

Html.Partial("partialViewName", newModel);

You cannot reach the Model which was sent for parentView. Therefore, from now on the Model which is active in the partialViewName is the newModel. The viewData which is send for parentView can be used also for partialViewName.

> As a special case, when you use Html.Partial and if you want to send ViewDataDictionary..

The Model which is send for parentView can be used also for partialViewName

I.

@Html.Partial("partialViewName", new ViewDataDictionary { { "key", value }, { "key2", value2 }  })

Here, the ViewData which was sent for parentView overwrite by 'new ViewDataDictionary'.

Here, If there is a ViewBag which is for parentView, you cannot reach that if you write the code like above one.

II.

ViewDataDictionary viewDataDictionary =  new ViewDataDictionary();
viewDataDictionary.Add("key", value);
viewDataDictionary.Add("key2", value2);
@Html.Partial("partialViewName", viewDataDictionary)

This usage is same as first one (I.).

III.

ViewDataDictionary viewDataDictionary = ViewData; //If you use this code block,  ViewBag which is sent for parent View is not lost.
viewDataDictionary.Add("key", value);
viewDataDictionary.Add("key2", value2);
@Html.Partial("partialViewName", viewDataDictionary)

With this code block, You can reach the ViewData and ViewBag which are sent for parentView in the partialViewName

Answer 6

Recently I was experiencing same problem, but the answers here were just workarounds as they propose not to use the overload of Html.Partial using viewData. But if you had to use these overloads I believe the correct answer is:

@Html.Partial(
     "PartialViewName",
     model_object,
     new ViewDataDictionary() { { "Value1InViewBag", ViewBag.Value1InViewBag }, { "Value2InViewBag", ViewBag.Value2InViewBag } }
)

I think this answer should be used if you need to pass different ViewDataDictionary (e.g. I us it for changing HtmlFieldPrefix) and because in the view you should know, what partial view wil need in ViewBag, so it should not be problem to name all the parameters from ViewBag to be copied into new ViewBag used in partial view (apparently ViewBag uses values from ViewData).