Skip to main content

Create a Schema using TOM.Net API

I was a little frustrated today for not finding out soon enough about the SchemaFields class. Basically that's the class you need when creating a Schema programmatically using TOM.Net API in SDL Tridion 2011.

Creating the Schema is easy -- just use the new Schema(session, parentTcmUri) constructor, but creating the fields themselves is a bit tricky. You have to use the SchemaFields class, just like you would use ItemFields on a normal Component fields or on any Metadata fields collections.

The code below creates a Schema and adds one RTF field to it and one Keyword based field to its metadata fields:

Session session = new Session();

Schema schema = new Schema(session, new TcmUri("tcm:20-1-2")) {
    Title = "New Schema",
    Description = "Schema Description"

SchemaFields fields = new SchemaFields(schema);
fields.Fields.Add(new XhtmlFieldDefinition("NewField") {
    Description = "New Field Description",
    MinOccurs = 1, // mandatory
    Height = 5

KeywordFieldDefinition metaField = new KeywordFieldDefinition("MetaField") {
    Description = "New Meta Field Description",
    Category = new Category(new TcmUri("tcm:20-859-512"), session)
metaField.List.Type = ListType.Tree;

schema.Xsd = fields.ToXsd();

Having problems creating a Session object? Have a look at my other post describing how to fix Session creation.


Popular posts from this blog

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

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

Event System to Create Mapped Structure Groups for Binary Publish

As a continuation of last week's Publish Binaries to Mapped Structure Group , this week's TBB is in fact the Event System part of that solution. Make sure you do check out the previous post first, which explains why and what this Event System does. To reiterate, the Event System intercepts a Multimedia Component save, take its Folder path and create a 1-to-1 mapping of Structure Groups. The original code was written, again, by my colleague Eric Huiza : [ TcmExtension ( "MyEvents" )] public class EventsManager  : TcmExtension {     private Configuration configuration;     private readonly Regex SAFE_DIRNAME_REGEX = new Regex ( @"[\W_]+" );     public EventsManager() {         ExeConfigurationFileMap fileMap = new ExeConfigurationFileMap ();         fileMap.ExeConfigFilename = Path .GetDirectoryName( Assembly .GetExecutingAssembly().Location) + "\\EventSystem.config" ;         configuration = ConfigurationManager