3. The File Browser : Caution on Reusing the Name of a Renamed Element

Caution on Reusing the Name of a Renamed Element
The ability to reuse the name of a renamed element provides significant flexibility for project refactoring tasks. But it also introduces a complication: what happens if you rename an element, create a new element at the same pathname, then invoke the Revert to Backed command on the renamed element?
The renamed element cannot revert to its old pathname, because there’s a new element at that pathname. The original element simply disappears from your workspace. You might wonder “Why does the element not get (stranded) status?” The Revert to Backed command makes an element inactive in the workspace. The (stranded) status applies only to active elements.
At this point, your workspace contains a new element at the given pathname, and the parent stream contains the original element at that pathname. Attempting to promote the new element would produce a 'name already exists in parent stream' error. Use one of the following procedures to return this pathname to a consistent state:
If you want to return to using the original element
1.
2.
3.
4.
5.
If you want to discard the original element and use the new element
These steps must be performed with the AccuRev CLI, which supports defuncting of the "disappeared" element using its element-ID.
1.
2.

AccuRev, Inc.
Phone: 781-861-8700
Fax: 781-861-8704
support@accurev.com