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.



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...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...