# Renaming Bentley Features

# Introduction

The collected data for feature names are code-based. Configure bentley_feature_rename.map to rename Bentley features. The new feature names will be visible in the historical reports.

Apply the configurations shown in the Open iT server.

# Configuring `bentley_feature_rename.map`

Open bentley_feature_rename.map in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

Notice that it contains instructions on how to edit the file.
Specify the Bentley feature to rename with the following syntax:
Mapping Syntax
```
MAP: NewFeatureName 
OldFeatureName1
```
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'BentleyFeature' and 'bentleyfeature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: MicroStation
1000
```
This example renames all of the 1000 features to MicroStation.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

Open bentley_feature_rename.map in the etc directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\.

Notice that it contains instructions on how to edit the file.
Specify the Bentley feature to rename with the following syntax:
Mapping Syntax
```
MAP: NewFeatureName 
OldFeatureName1
```
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'BentleyFeature' and 'bentleyfeature', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: MicroStation
1000
```
This example renames all of the 1000 features to MicroStation.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

Licusage

(126) License Peak Usage Distinct Host
(127) License Host User Usage Distinct Host
(128) Usergroup License Use Distinct Host

# Next Steps?

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the historical reports.

Data Generation

# Renaming Bentley Features

# Introduction

# Configuring bentley_feature_rename.map

# Next Steps?

# Configuring `bentley_feature_rename.map`