MSC Nastran > Read Input File > 5.3 Conflict Resolution
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
5.3 Conflict Resolution
If an entity can not be imported into Patran because another entity already exists with that ID or name, then the conflict resolution logic is used. There are 2 different approaches taken, depending on whether the entity is identified by an ID or by a name.
Conflict Resolution for Entities Identified by IDs
If a new definition conflicts with a definition already in the Patran database, you will be asked if you want the ID of the new definition offset. If you select YES, a new ID will be chosen. If you select YES FOR ALL, a new ID will be chosen for this definition, as well as for any others found to be in conflict. In this case, then all references to the ID in the original Patran database will still reference the old ID, but references to the ID from within the input file will be altered to reference the new ID.
If you do not want the CID to be offset, then you will be asked if you want the new definition to overwrite the existing definition. If this is done, then all references to this ID from both the original Patran database and the input file will be referencing the same ID. The definition for that ID will be either the old or the new definition, depending on how this second question is answered.
Conflict Resolution for Entities Identified by Names
The user is not asked what to do in cases where the conflicting entities are identified by names. The name for the new entity will be modified by appending an extension to the name. The new name will be “<old name>.r<n>”. The value of n is chosen to make the new name unique.
No merging of data or application regions is done. The old definition is left unchanged.