Error Messages/NameCollision
Error Message
Cause
This message occurs when you add a Module or Library to your model, and an object within the Module being added has the same identifier as an object in your model. Since all objects must have unique identifiers, there is a name conflict.
To avoid name conflicts when refreshing a module already in memory with a newer version, be sure to select Merge when adding the module. When you select Merge, name conflicts do not occur -- or more precisely, when they do occur, they are assumed to be the same object, so you don't see this error.
Options
Yes
The object already in memory is renamed. The object being loaded retains the original name.
Note: You might wonder why it isn't the other way around. To see why the existing object is the one that gets renamed, consider what happens when you are loading a linked module or library. That linked module might be shared with other models. Because it is linked, any changes (including this rename) would be written back to its original file, and the module/library would no longer work with other models that use it.
No
When you press No, the object being loaded is not included. This usually means that your module is incompletely loaded. You can delete the module node and try again later.
Repeat for all
Checking this box will repeat your response for any other name collisions that occur during this Add Module... or Add Library operation.
Enable comment auto-refresher