Skip to main content

Rename Schema Field XML Name

The following always happens in an implementation -- some field in a Tridion Schema has a wrong "XML Name". Maybe it's capitalized wrong, or just a silly name that doesn't reflect what the field should be. In any case, you just want to rename it. Yes, I know you should not touch XML Names after the Schema has been created and after content has been entered. I still want to do it.

But, there is one problem though, you will lose all your content in that field in all the Components on that Schema. The reason is that the content in a Component is represented as XML where each Schema field "XML Name" is well, the name of each element in the XML. Changing the Schema "Xml Name" will basically change the XSD of the Component XML, immediately rendering it invalid.

There are several solutions to this issue and below is the one I just used in order to rename such XML Name:
  1. Create an additional field in the Schema where the only thing that differs from the original field we want to rename is the "XML Name". All other attributes, such as type, mandatory, single- vs multi-value, etc. are simply kept the same;
  2. If original field is mandatory, change it to optional;
  3. Run the RenameField tool (presented below), which will rename the old field to the new field for each Component on a given Schema;
  4. Remove the old field from the Tridion Schema;
  5. (optional) Run the RenameField tool again, just to make sure and re-sync all Components on their modified Schema. This step is optional, but I personally like to do it;
Creating a new Schema field will basically allow us to take the old field, rename it to the new field and save the Component with the new structure. In order to automate this process, I created a little Console application in .NET, which uses CoreService to communicate with your Tridion Content Manager and perform the modifications for each Component on a given Schema.

The RenameField tool follows the following logic:
  • Open a connection to the CoreService endpoint (basic HTTP, so it can be used from any client that can access the TCM instance);
  • Run a 'Where Used' query on a given Schema, retaining only Components. This will technically give us all Components that are 'based-on' our Schema;
  • For each Component:
    • Read the Component data
    • Either on Content (or Metadata) XML, read the old field XML node
    • Create a new XML node using the new field name
    • Move all attributes from the old node to the new node
    • Move all child nodes from the old node to the new node
    • Replace old node with new node
    • Save Component back to TCM
Once the tool has executed, the old nodes will not exist anymore in the Component. It is now safe to remove the old field from the Schema.

Since the Component XML doesn't contain any node with the old "XML Name", it is not necessary to re-sync the Components on the new Schema, but it is possible to do so by simply running the RenameField tool again.

The RenameField tool is available on my Git page under Rename Schema Field.

The tool takes a few parameters in its App.config or executable .config file. Their values should be self-explanatory.

As always, first DO BACKUP your CM database before running this tool, because it will modify your content and create new versions on Components!


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

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