MVC 3 (C#, ASP.NET 4) Child records page - help needed with example

Hi,
I am having a really hard time finding a simple example of creating a view and related changes to model/controller(s) to display a child record <view>.

In other words - I am not trying to accomplish fancy master-detail display and CRUD operations on one view,

I just want to add an action on the master/parent records view, to open/jump to a <filtered?> child/detail view page.

This seems like an obvious thing, that you couldn't NOT have in an application  - but I can't seem to find a good simple example of it anywhere !

Sure it would be noce to have a list of child records on a master page as well - but right now I am just trying to wrap my head around this simple task !

And yes - I am just getting started with MVC + ASP.NET ;-)
bbaleyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bbaleyAuthor Commented:
I forgot to mention;

the model already has defined the EntityCollection/navigation/relationshipmanager/getrelatedcollction stuff related to the child/detail tables- which came from the Model Designer and db relationships - this was *not* CodeFirst....

for instance;

        #region Navigation Properties
   
        /// <summary>
        /// No Metadata Documentation available.
        /// </summary>
        [XmlIgnoreAttribute()]
        [SoapIgnoreAttribute()]
        [DataMemberAttribute()]
        [EdmRelationshipNavigationPropertyAttribute("UGOPSModel", "FK_BargeDetail_Shift", "BargeDetail")]
        public EntityCollection<BargeDetail> BargeDetails
        {
            get
            {
                return ((IEntityWithRelationships)this).RelationshipManager.GetRelatedCollection<BargeDetail>("UGOPSModel.FK_BargeDetail_Shift", "BargeDetail");
            }
            set
            {
                if ((value != null))
                {
                    ((IEntityWithRelationships)this).RelationshipManager.InitializeRelatedCollection<BargeDetail>("UGOPSModel.FK_BargeDetail_Shift", "BargeDetail", value);
                }
            }
        }
0
Bob LearnedCommented:
Let me start by saying that I am trying to learn about MVC 3, since it is a little different than MVC 2.

Are you using Razor or ASP.NET views?

Parent Child List in MVC3 Razor
http://stackoverflow.com/questions/9341711/parent-child-list-in-mvc3-razor

@model IEnumerable<Product>
<ul>
    @foreach (var child in Model)
    {
        <li>
            @Html.DisplayFor(m => child.Name)
            @Html.Action("DisplayChildren", "ControllerName", 
                new { parentId = child.Id })
        </li>
    }
</ul>

Open in new window

0
ambienceCommented:
>> I just want to add an action on the master/parent records view, to open/jump to a <filtered?> child/detail view page.

This requires State, because the action depends upon the state (model) of the previous action. The way to do this is to either store in session the parent model and execute second action on say ChildController. The action would fetch the stored parent from session. Of course, using session is a decision that affects scalability of applications and for this simple learning task I suggest that you try it that way.

Another solution is to pass the parent's id to child action (store it as part of the url for action on main page). The child controller can re-fetch the parent object or perhaps just fetch collection of objects for given parent id. The downside is an additional DB hit.

Another interesting solution (which may not make sense in all cases) would be to store the json form of object on the client side will relationships eagerly loaded. Then for just child display, you can work entirely with Js and client end html.
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

bbaleyAuthor Commented:
:Abience;

Seriously?
It's this difficult ?

What application does NOT require the editing of child/detail records ?

How else could you possibly drill down into detail records ?

I just find it so hard to believe this requires any special handling and/or difficult to locate a "best practices" approach to doing so.
0
ambienceCommented:
Not its not difficult - and every application that needs such a functionality also has to obtain the child object somehow

- Find it already stored in session  - stateful design
- Find it from datasource, need to know the child id - stateless design.

The main issue here is that it requires two HTTP request

1) fetch parent and display an edit link
2) open a page filled with children from previous request

The third approach (JSON) I mentioned tries to cache everything on the client side on first request and saves hitting the server again just to open a form.

>> How else could you possibly drill down into detail records ?

Normally from a master-detail list page you open directly the child edit page by passing it the child's id. Sophisticated solutions would put the retrieved children in a Cache like ASP.NET Cache.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bbaleyAuthor Commented:
"The main issue here is that it requires two HTTP request

1) fetch parent and display an edit link
2) open a page filled with children from previous request"

----------------------------------------------

Thank you for the explanation -
this is what I am having a hard time finding an easy example of.


I found a project on MS asp.net MVC tutorial site - and it gives code-first examples of DISPLAYING a list of child records, so that's a good starting point, but it has no explanation - only code.

So I am trying to matchup the difference between the code-first examples and my non-code-first model and the different way of coding things...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.