Skip to main content

SDL Web 8 - Move Item in BluePrint using Core Service

As a follow-up on the previous post Move Items Between Publications, I created a simple command line utility that promotes or demotes an item using Core Service.

The program is available in this blog's GitHub repository BluePrint Move Item.

Usage parameters:
  • promote | demote -- the action to perform
  • itemTcmUri -- the item to move
  • destinationPublicationTcmUri -- the Publication to move item to

The .config file specifies the Core Service endpoint and basicHttp user/password. Note the new endpoint for SDL Web 8:

    http://cem.tridion.com/webservices/CoreService201501.svc

The following example promotes (moves up) an item to a parent Publication:

Mitza.MoveItem.exe promote tcm:3-37 tcm:0-2-1
Connect to CoreService http://cme.tridion.com/webservices/CoreService201501.svc/basicHttp
Connected as Administrator (IP-AC150874\Administrator)
Original item:  tcm:3-37 | Publication: "020 Content"
Moved item:     tcm:2-37 | Publication: "010 Schema"

The following example demotes (moves down) an item to a child Publication:

Mitza.MoveItem.exe demote tcm:2-37 tcm:0-3-1
Connect to CoreService http://cme.tridion.com/webservices/CoreService201501.svc/basicHttp
Connected as Administrator (IP-AC150874\Administrator)
Original item:  tcm:2-37 | Publication: "010 Schema"
Moved item:     tcm:3-37 | Publication: "020 Content"

The code highlights below are the actual worker methods:

    client.Promote(itemId, destinationPublicationId, instruction, readOptions);
    client.Demote(itemId, destinationPublicationId, instruction, readOptions);

where the instruction object defines how to deal with errors/warnings, and it can be configured to fail on Warnings or just on Errors:

    OperationInstruction instruction = new OperationInstruction { Mode = OperationMode.FailOnError };

The result of the promote/demote method is an object of type OperationResultDataOfRepositoryLocalObjectData that contains the possible warnings in the result and the result object data itself.

    OperationResultDataOfRepositoryLocalObjectData result = client.Promote(componentId, destinationRepositoryId, instruction, readOptions);
    if (result.ValidationWarnings.Length > 0)
    {
        Console.WriteLine("Validation warnings:");
        foreach (ValidationWarningData warning in result.ValidationWarnings)
        {
            Console.WriteLine("\tMessage:{0} | Source:{1} | Location:{2}",
                warning.Message, warning.Source, warning.Location);
        }
    }


Note that if a move operation fails, it will actually throw an exception and in its Message property we can find the reason(s) that caused the failure.



Comments

Popular posts from this blog

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

A DD4T.net Implementation - Custom Binary Publisher

The default way to publish binaries in DD4T is implemented in class DD4T.Templates.Base.Utils.BinaryPublisher and uses method RenderedItem.AddBinary(Component) . This produces binaries that have their TCM URI as suffix in their filename. In my recent project, we had a requirement that binary file names should be clean (without the TCM URI suffix). Therefore, it was time to modify the way DD4T was publishing binaries. The method in charge with publishing binaries is called PublishItem and is defined in class BinaryPublisher . I therefore extended the BinaryPublisher and overrode method PublishItem. public class CustomBinaryPublisher : BinaryPublisher { private Template currentTemplate; private TcmUri structureGroupUri; In its simplest form, method PublishItem just takes the item and passes it to the AddBinary. In order to accomplish the requirement, we must specify a filename while publishing. This is the file name part of the binary path of Component.BinaryConten

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