KM-Dim10: Alert - Dimensions CM 10.1.0 and 10.1.1 and Refactoring

ID:    A25
Published:    03 March 2008
Updated:    08 July 2008

Operating System(s)

  • AIX
  • All Windows
  • HPUX
  • Linux
  • SCO
  • Solaris
  • Unix
  • Windows 2000
  • Windows 2003
  • Windows 98
  • Windows NT
  • Windows XP


  • Dimensions CM


This applies to all Dimensions CM customers on versions 10.1 and 10.1.1 that are performing refactoring operations (remove, move and rename of files and folders) in projects that have attached deployment areas for stages other than the initial development stage.

When files or folders are refactored (removed, moved or renamed), the changes correctly take effect in the Dimensions project where development is taking place. However, the changes also take affect in all deployment areas associated with the project that contains the affected file/folder.

To clarify the issue, what follows is an example of how a rename of an item is propagated to areas attached to a project.

For this example, we will assume that there are four stages - "DEVELOPMENT", "UNIT TEST", "SYSTEM TEST" and "RELEASE" each of which have an attached deployment area. Imagine a Dimensions project contains a file called "src/examples/", for which a revision is currently deployed to "UNIT TEST".

This file is then renamed to "src/examples/". At that time Dimensions CM will correctly rename the file on disk in any areas associated with the "DEVELOPMENT" stage, but it will also rename the file on disk in any areas associated with "UNIT TEST", "SYSTEM TEST" and "RELEASE" stage

This issue was addressed in Dimensions CM 10.1.2. It is strongly recommended all customers using Dimensions CM deployment functionality to upgrade to Dimensions CM 10.1.2 or 10.1.3

A patch for Dimensions CM 10.1.1 is being worked on and will be made available very shortly.

Migration ID


Find Answers

Type a question or describe what you are looking for below

My Recent Searches

Welcome kb sso

Additional Assistance

  • Submit a Case Online
  • FAQs