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

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