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

Scaling Policies

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

Toolkit - Dynamic Content Queries

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

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