Skip to main content

SDL Web 8 - Move Items Between Publications

One of the new features in SDL Web 8 (scheduled to be released in early November, 2015) is "re-locating items in the BluePrint hierarchy". This long awaited functionality gives the possibility of moving items "up" and "down" between child-parent Publications.

Of course, the user must have permissions to perform the action. This means read, create, delete permissions on the old and new Publications, so that the items can be successfully relocated.

The operation checks first that all dependencies are available before performing the actual move. If there are any errors, they will be all shown. This is a change in the approach how errors are displayed. So, rather than showing one error at a time, all errors will be shown.

The walkthrough below shows a Component being promoted from Publication "010 Schema" to Publication "020 Content".

Initially, "My Article" resides in Publication "010 Schema"

In its original Publication "010 Schema", select the Component "My Article" and in context menu BluePrinting, select Demote.

Select BluePrinting Demote in original Publication

A dialog window pops-up, prompting the user to select the target Publication. This can be any Publication under the current Publication, in the same branch. Some limitations of Promote/Demote in BluePrint is that it can only move items in the same branch. It cannot move things into a sibling Publication, or into another BluePrint structure all together.

Select destination Publication

Clicking Demote will perform the actual move.

The Component "My Article" in the target Publication

The same functionality can be achieved also through the API. More information about that, in the next post Move Item in BluePrint using Core Service.


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