You can set preferences to enforce unique names for entities, tables, views, attributes, and columns. If you use naming standards, you must set these preferences for each model that you create. If you do not use naming standards, you can have modeling design problems that can produce errors when you run queries to extract particular sets of data. Duplicate names are not allowed for domain names and validation rules.
Note: Duplicate object naming preferences are not enforced when there are preexisting duplicate names, when attribute and column names are derived from domain inheritance, and when you copy an object. If you want all copied objects in a model to have unique names, you must manually change the names for each of them.
To set preferences for duplicate object names
The Model Naming Options dialog opens.
Specifies to allow duplicate names.
Note: Duplicate names are not allowed for domain names and validation rules.
Specifies to automatically rename the duplicate name by appending to the end of the name a forward-slash to indicate that the name has been used in the model and a number to indicate how many times (for example, MOVIE_COPY/2).
Specifies to provide a notification that a duplicate name exists and prompt you to enter a replacement name or accept the duplicate name. Replacement names are not checked for uniqueness.
Specifies to disallow the duplicate name. Duplicate names that you enter are deleted.
Duplicate object name preferences are set and the Model Naming Options dialog closes.
Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |