Skip to main content

A DD4T.net Implementation - Umbrella Model Builders

In a previous post I was presenting Umbrella Models and what they are useful for in DD4T. To recap a bit, we need these generic models when we have Component or Multimedia Links that can point to components based on several Schemas. In such case, we can't say for sure what is the type of the linked Component, and instead we need to use type ModelBase (presented in this post).

In this post I'll present the builders for such polymorphic links. Let's first assume we have a Device model that has a Component link field that accepts several Schemas:

    public class Device : ModelBase
    {
        /// <summary>
        /// Could be a heterogenous collection of: Internal Link, External Link
        /// </summary>
        public IList<ModelBase> RelatedItems { get; set; }


The Device model builder needs to be able to identify the type of the linked RelatedItems and build the right model for it. As such, we have the following code in the DeviceBuilder class:

    Device device = new Device(component)
    {
        RelatedItems = RelatedItemBuilder.Instance.Build(fields.LinkedComponentValues("Right_Related_Items"))


The code simply invokes an umbrella builder (i.e. RelatedItemBuilder) that knows how to build the actual model Internal Link or External Link. The umbrella builder sample code looks like this:

    public class RelatedItemBuilder : Builder<IComponent, ModelBase>
    {
        private static readonly RelatedItemBuilder _instance = new RelatedItemBuilder();
        public static RelatedItemBuilder Instance { get { return _instance; } }

        private RelatedItemBuilder() {}

        public override ModelBase Build(IComponent component)
        {
            ModelBase model = null;

            switch (component.Schema.Title)
            {
                case Constants.INTERNAL_LINK_SCHEMA:
                    model = InternalLinkBuilder.Instance.Build(component);
                    break;

                case Constants.EXTERNAL_LINK_SCHEMA:
                    model = ExternalLinkBuilder.Instance.Build(component);
                    break;
            }

            return model;
        }


In this case I chose to filter the type of a Component based on its Schema title. A better solution would be to filter based on Schema root element name. This is not always possible, because the root element name must be changed proactively at the moment when the Schema is created or at least before creating many Components on it.

Based on the Schema title (or root element name), we identify the right builder and, as such, we invoke the respective builder.


Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...