Skip to main content

Create Embedded Fields Programmatically

Image
By
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)


Labels:

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
13 February, 2013 15:03
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.
03 April, 2013 20:27
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.
03 April, 2013 20:33
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 :)
03 April, 2013 20:50
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 :)
03 April, 2013 20:54
Post a Comment

Popular posts from this blog

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

Toolkit - Dynamic Content Queries

By
This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio
Post a Comment
Read more

Running sp_updatestats on AWS RDS database

By
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
1 comment
Read more