Desktop Client supports the rename of objects that changes the name and updates the unique identifier (UID) and unique key when they contain the name. Data Validator supports the ability to rename objects using object mapping, and the specific object action Rename has been created for this purpose.
The Data Validator rename functionality relies on the UID definitions in the staging area matching the UID definitions in the target system. UID definitions must be set on all objects that Data Validator exports from the staging area. When you create your mappings, you must set the correct UID in the import mapping by setting the UID definitions in any object mapping. For more information, see Define column headers.
The primary intention of the rename mapping is to change the name, it is not recommended to use rename for updating properties. For documents, the rename functionality in SmartPlant Foundation renames the Master, all revisions, all versions, and updates the UIDs on all relationships.
For more information, see Configure unique identifiers.
DEVTag rename mapping example
This is an example mapping for a Tag using the rename action, where the column names are OLDNAME, NEWNAME, AREA, and PLANTCODE.
Design document master rename mapping
This is an example mapping for a design document using the rename action, where the column names are OLD_DOCUMENT, NEW_DOCUMENT, and CONFIG.
