Skip to main content

Templating Parameter Double Lookup

In Tridion templating, double look-up refers to a technique of reading package values two or more times. This is probably most commonly used when reading TBB parameters.

For example, let's consider a TBB that takes a parameter called 'inputValue' of type String, which represents a TcmUri. In Template Builder, the template developer can specify a value for 'inputValue' in several ways:

  • hard-code an actual TcmUri, e.g. tcm:1-2;
  • use a package item name - e.g. package item named MyVariable, whose value is the TcmUri;
  • use a Dreamweaver Language Expression - e.g. Component.Fields.BannerImage that resolves to a TcmUri;

Hard-Coded Value
The look-up in the package is direct:

var value = package.GetValue("inputValue");

Package Item Name
I need to first look-up the package item, and then take its value. This is a form of double look-up:

var paramInputValue = package.GetValue("inputValue");
Item valueItem = package.GetByName(paramInputValue); // double look-up
var value = valueItem.GetAsString();

Alternatively, the package item name look-up can be done using Dreamweaver Language Expressions, see next. The two are thus equivalent.

Dreamweaver Language Expressions
You can also use a double look-up, much like the package item name:

var paramInputValue = package.GetValue("inputValue");
var value = package.GetValue(paramInputValue);

Why Stop at Double Look-Up?
Why not have triple look-up, or better yet N-look-up? Well, probably not very likely to use these cases, but technically, they are definitely possible.

var value = package.GetValue("inputValue");
String aux = package.GetValue(value);

while (aux != null) {
    value = aux;
    aux = package.GetValue(value);

Putting it All Together
string imageTcmUri = m_Package.GetValue("ImageTcmUri"); // direct look-up
if (String.IsNullOrEmpty(imageTcmUri))
     throw new Exception("Mandatory parameter ImageTcmUri cannot be empty");
else if (!TcmUri.IsValid(imageTcmUri)) // give second chance
     imageTcmUri = m_Package.GetValue(imageTcmUri); // double lookup
     if (String.IsNullOrEmpty(imageTcmUri) || !TcmUri.IsValid(imageTcmUri)) // fail
          throw new Exception("Invalid parameter ImageTcmUri");


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: I stumbled upon the following post from 2008 (!!!), , 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

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven