The tool does not rename layers, since a layer is a reference to a dataset.
The tool does not rename fields in the dataset. For example, if you have a field named ROADS_ID in a feature class named Roads, renaming the Roads feature class to Streets does not rename the ROADS_ID field to STREETS_ID.
The tool does not work with data stored in a DB2 database due to database constraints.
This parameter is only necessary in the event of a name conflict between two different data types. For example, a geodatabase can contain a relationship class with an identical name to a feature class. If that is the case, specify the relevant keyword.
FeatureClass—In the event of duplicate names, the feature class will be used.
FeatureDataset—In the event of duplicate names, the feature dataset will be used.
MosaicDataset—In the event of duplicate names, the mosaic dataset will be used.
ParcelFabric—In the event of duplicate names, the parcel fabric will be used.
RelationshipClass—In the event of duplicate names, the relationship class will be used.
Topology—In the event of duplicate names, the topology will be used.
This parameter is only necessary in the event of a name conflict between two different data types. For example, a geodatabase can contain a relationship class with an identical name to a feature class. If that is the case, specify the relevant keyword.
FeatureClass—In the event of duplicate names, the feature class will be used.
FeatureDataset—In the event of duplicate names, the feature dataset will be used.
MosaicDataset—In the event of duplicate names, the mosaic dataset will be used.
ParcelFabric—In the event of duplicate names, the parcel fabric will be used.
RelationshipClass—In the event of duplicate names, the relationship class will be used.
Topology—In the event of duplicate names, the topology will be used.
String
Code sample
Rename example 1 (Python window)
The following Python window script demonstrates how to use the Rename function in immediate mode.