Databases
StackOverflow2013
Postsdbo
POMVC .Net view nested list of models
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMVC .Net view nested list of models
    primarykey
    data
    text
    <p>I have an abstract class with 3 other classes that inherit from this class:-</p> <pre><code>public abstract class AbstractTask { [Key] public int ID {get; set;} [DisplayName("Featured Task")] public bool Featured { get; set; } // various other properties } public class HighLevelTask : AbstractTask { [DisplayName("Workstream Description")] public String Workstream { get; set; } public virtual ICollection&lt;MidLevelTask&gt; MidLevelTasks { get; set; } } public class MediumLevelTask : AbstractTask { public int HighLevelTaskID { get; set; } public virtual ICollection&lt;DetailLevelTask&gt; DetailLevelTasks { get; set; } } public class DetailLevelTask : AbstractTask { public int MidLevelTaskID { get; set; } } </code></pre> <p>So a High Level task can contain any number of Mid Level tasks and a Mid level task can contain any number of Detail tasks. Tasks at any level can be set as 'Featured' by the property inherited from the abstract class.</p> <p>In a HTML view I want to present a nested list of the 'featured' tasks. So I am thinking in a Controller action something like this to collect all the featured tasks but am at a mental block on the best way to present this.</p> <pre><code> var qryHighLevelTasks = from t in context.HighLevelTasks where t.Featured == true select t; var rsHighLevelTasks = qryHighLevelTasks.ToList(); foreach(var highLevelTask in rsHighLevelTasks) { // get all mid level featured tasks related to this high level task var qryMidTasks = from midLevelTasks in context.MidLevelTasks where midLevelTasks.Featured == true &amp;&amp; midLevelTasks.HighLevelTaskID == highLevelTask.ID select midLevelTasks; var rsMidLevelTasks = qryMidTasks.ToList(); foreach (var midLevelTask in rsMidLevelTasks) { // get all detail level featured tasks related to this mid level task var qryDetailTasks = from detailLevelTasks in context.DetailLevelTasks where detailLevelTasks.Featured == true &amp;&amp; detailLevelTasks.MidLevelTaskID == midLevelTask.ID select detailLevelTasks; var rsDetailLevelTasks = qryDetailTasks.ToList(); } } </code></pre> <p>Perhaps I should have a composite model to represent the featured tasks? Or is there a better way? Any recommendations?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USEL Yusubov
    1. USGordon Hickley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMVC .Net view nested list of models
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POMVC .Net view nested list of models
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMVC .Net view nested list of models
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would create a viewmodel, more code, but far more readable
      singulars
      1. POMVC .Net view nested list of models
      1. USSteve B
    2. COIt would be better to consider a 'Partial View' to render the nested list of the 'featured tasks'. In addition, try to focus on your view-model first. You may have a collection of 'featured tasks' in your view-model, and pass these collection to your partial view to be rendered.
      singulars
      1. POMVC .Net view nested list of models
      1. USEL Yusubov
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload