Nested Data Models

Nested data models allow you to define a model that can be used as child property of another data model.

This is useful for creating rich data structures for your block types and custom entities, and enables the creation of more complex components such as multi-layered menus, advanced carousels and other nested content scenarios.

There are two types of nested data model annotations:

• [NestedDataModelCollection]
• [NestedDataModelMultiTypeCollection]

Each of these annotations are explained further down the page, but first we need to understand how to define a nested data model.

Defining a Nested Data Model

A nested data model is simply a class that inherits from INestedDataModel. You can add any properties you like and annotate them in the same way you would with any other data model. You can even recursively reference the same nested data model inside itself, which can be useful for building hierarchical data structures such as menus.

The following example represents one slide in a carousel:

using System.ComponentModel.DataAnnotations;
using Cofoundry.Domain;

public class CarouselSlideDataModel : INestedDataModel
{
    [PreviewImage]
    [Display(Description = "Image to display as the background tot he slide.")]
    [Required]
    [Image]
    public int ImageId { get; set; }

    [PreviewTitle]
    [Required]
    [Display(Description ="Title to display in the slide.")]
    [MaxLength(100)]
    public string Title { get; set; }

    [Display(Description ="Formatted text to display in the slide.")]
    [Required]
    [Html(HtmlToolbarPreset.BasicFormatting)]
    public string Text { get; set; }
}

Note that the display preview set of attributes can be used to control which properties display as columns in a selection grid.

The next section shows you how you can use this data model to create the data model for a carousel.

[NestedDataModelCollection]

The [NestedDataModelCollection] attribute is used to mark a property that contains a collection of nested data model types.

Optional Properties

• MinItems: The minimum number of items that need to be included in the collection. 0 indicates no minimum.
• MaxItems: The maximum number of items that can be included in the collection. 0 indicates no maximum.
• IsOrderable: Set to true to allow the collection ordering to be set by an editor using a drag and drop interface. Defaults to false.

Example

This example uses the CarouselSlideDataModel defined in the last section.

using System.ComponentModel.DataAnnotations;
using Cofoundry.Domain;

public class CarouselDataModel : IPageBlockTypeDataModel, IPageBlockTypeDisplayModel
{
    [MaxLength(100)]
    [Required]
    public string Title { get; set; }

    [Required]
    [NestedDataModelCollection(IsOrderable = true, MinItems = 2, MaxItems = 6)]
    public ICollection<CarouselSlideDataModel> Items { get; set; }
}

[NestedDataModelMultiTypeCollection]

The [NestedDataModelMultiTypeCollection] data annotation can be used to decorate a collection of NestedDataModelMultiTypeItem objects, indicating the property represents a set of nested data models of mixed types. The types must be defined in the attribute constructor by passing in a type reference for each nested data model you want to be able to add.

Optional Properties

• MinItems: The minimum number of items that need to be included in the collection. 0 indicates no minimum.
• MaxItems: The maximum number of items that can be included in the collection. 0 indicates no maximum.
• IsOrderable: Set to true to allow the collection ordering to be set by an editor using a drag and drop interface. Defaults to false.
• TitleColumnHeader: The text to use in the column header for the title field. Defaults to "Title".
• DescriptionColumnHeader: The text to use in the column header for the description field. Defaults to "Description".
• ImageColumnHeader: The text to use in the column header for the image field. Defaults to empty string.
• TypeColumnHeader: The text to use in the column header for the model type field. Defaults to "Type".

Example

The following example shows a property that links to different types of social media profiles.

using Cofoundry.Domain;

public class ExampleDataModel : ICustomEntityDataModel
{
    [NestedDataModelMultiTypeCollection(
        new Type[] {
            typeof(FacebookProfileDataModel),
            typeof(TwitterProfileDataModel),
            typeof(LinkedInProfileDataModel),
            typeof(BlogLinkDataModel)
        },
        IsOrderable = true,
        MinItems = 1,
        MaxItems = 3,
        TitleColumnHeader = "Profile"
        )]
    public ICollection<NestedDataModelMultiTypeItem> SocialProfiles { get; set; }
}

Output:

The nested data models references in the example are shown below:

using Cofoundry.Domain;

[Display(Name = "Facebook")]
public class FacebookProfileDataModel : INestedDataModel
{
    [Display(Name = "Facebook Id")]
    [PreviewTitle]
    public string FacebookId { get; set; }
}

[Display(Name = "Twitter")]
public class TwitterProfileDataModel : INestedDataModel
{
    [PreviewTitle]
    public string TwitterHandle { get; set; }
}

[Display(Name = "LinkedIn")]
public class LinkedInProfileDataModel : INestedDataModel
{
    [Display(Name = "Profile Id")]
    [PreviewTitle]
    public string ProfileId { get; set; }
}

[Display(Name = "Blog")]
public class BlogLinkDataModel : INestedDataModel
{
    [PreviewTitle]
    [Url]
    public string Url { get; set; }
}

Further Examples

You can find a full walk through of nested data models on our blog, and more examples in our Menus and Page Block Types samples projects.