The CLR-Name property specifies the name that will be used to refer to the instance of the entity from Code Expressions in Adapterflows.
The CLR-name is automatically generated from the Name property if left empty when creating a new entity, but can be modified (except for Adapterflow entities).
The CLR-name must be unique within the context of the entity, which means that two Node attributes cannot have identical CLR-names, two partner attribute types in the same group cannot have identical CLR-names etc. However, two partner attribute types in different groups can have the same CLR-name, since the CLR-name of the group will prevent confusion.
A CLR-name must be a legal C# identifier name. This means, for example, that it cannot start with a number, must consist only of letters, numbers and underscores, it must not be equal to a reserved word in C#, etc.
A CLR-name must not start with the reserved word "__icore"
The CLR-name for an entity type may have further restrictions, such as reserved words that cannot be used in the name. These are are:
For Setting attribute group:
For Partner attribute group:
Changing a CLR-Name property
The CLR-Name property is modifiable, except on Adapterflow entities where it is read-only.
Changing the CLR-name of an entity requires refactoring all Adapterflows with code expressions referring to this entity. The process may take several minutes to complete and requires that no Adapterflow in the system contains errors, but can be recompiled. When trying to change the CLR-name of an entity in the administrator, a confirmation dialog is displayed. The dialog contains a message notifying of the required refactoring, allowing the user to select to cancel any pending changes or start the refactoring.