Skip to main content

Create Embedded Fields Programmatically

During on the my Event Systems, I came across the requirement of creating (and populating) new Embedded Schema fields.

To do so, I still used the ItemFields collection, which has a constructor accepting a Schema parameter. This is the one to use, but the counter-intuitive part was to obtain the Embedded Schema. I ended up getting it from the field definition of the 'outer' Schema field.

Finally notice that when the Component needs to be saved, the ItemFields collection needs first be saved into the Component's content.

ItemFields fields = new ItemFields(component.Content, component.Schema);
EmbeddedSchemaField linksField = fields["Links"] as EmbeddedSchemaField;
EmbeddedSchemaFieldDefinition linksFieldDefinition = linksField.Definition as EmbeddedSchemaFieldDefinition;

ItemFields newItemField = new ItemFields(linksFieldDefinition.EmbeddedSchema);
((ComponentLinkField)newItemField["Component"]).Value = anotherComponent;
((NumberField)newItemField["Version"]).Value = 13;

linksField.Values.Add(newItemField);

component.Content = fields.ToXml();
component.Save(true);

The whole code above runs inside the method ComponentPostSavedEvent(Component component, SaveEventArgs args, EventPhases phase)


Comments

Anonymous said…
It is a good example, but I cannot save component, because this is TOM.NET API, a it is "read only". I get error: 'Tridion.ContentManager.IdentifiableObject.Save()' is inaccessible due to its protection level when I try to save component. Any suggestions please.

Thanks,
Milos
Hao Houang said…
Very useful! I needed to do a check when user saves a Component to check an embedded schema field which contains a Multimedia link. If the Multimedia link is empty, we have it point to a dummy image. Since this is when the Component is saved, I attached it to the ComponentPreSaveEvent and just used Component.Save() without the boolean to check in the item since that will be done automatically after my code is executed.
Nivlong said…
Cool, I would have assumed we'd want to set a default in the schema definition, but I see where the Event System gives you flexibility to have that default image in a lower publication or even have logic on which "default" to set.
Mihai Cădariu said…
Milos - are you getting this error in templating (the example above is from event system)? To enable read-write in templates, you can modify TridionContentManager.config and set <templating allowWriteOperationsInTemplates="true" />

Hao - you owe me a drink now :)
Hao Houang said…
Indeed. I already have the default value set but this is a scenario where the client likes to copy old Component and modify instead of creating a new Component. Therefore the Multimedia link is already using an old image and they want to clear it out and save. Therefore it makes more sense with the Event system to add that value in :)

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

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