Setting CDM/LDM Model Options

You can set CDM/LDM model options by selecting Tools > Model Options or right-clicking the diagram background and selecting Model Options.

You can set the following options on the Model Settings page:



Name/Code case sensitive

Specifies that the names and codes for all objects are case sensitive, allowing you to have two objects with identical names or codes but different cases in the same model. If you change case sensitivity during the design process, we recommend that you check your model to verify that your model does not contain any duplicate objects.

Enable links to requirements

Displays a Requirements tab in the property sheet of every object in the model, which allows you to attach requirements to objects (see Requirements Modeling).

Enforce non-divergence

Specifies that attributes attached to a domain must remain synchronized with the selected properties (see Controlling Non-Divergence from a Domain).

Use data type full name

Specifies that the complete data type is displayed in entity symbols.

Default data type

Specifies the default data type to apply to domains and attributes if none is selected for them.

External Shortcut Properties

Specifies the properties that are stored for external shortcuts to objects in other models for display in property sheets and on symbols. By default, All properties appear, but you can select to display only Name/Code to reduce the size of your model.
Note: This option only controls properties of external shortcuts to models of the same type (PDM to PDM, EAM to EAM, etc). External shortcuts to objects in other types of model can show only the basic shortcut properties.


You can choose between the following notations:

  • Entity / Relationship [Default – used throughout this manual] Entity/relationship notation connects entities with links representing one of four relationships between them. These relationships have properties that apply to both entities involved in the relationship

  • Merise - uses associations instead of relationships

  • E/R + Merise - both entity/relationship and Merise are used in the same model

  • IDEF1X - data modeling notation for relationships and entities. In this notation, each set of relationship symbols describes a combination of the optionality and cardinality of the entity next to it

  • Barker – inheritances are represented by placing the child entities inside the parent entity symbol, and relationships are drawn in two parts, each reflecting the multiplicity of the associated entity role.

For more information about these notations, see Supported CDM/LDM Notations

Unique code

Requires that data items or relationships have unique codes

Allow n-n relationships

[LDM only] Allows n-n relationships to be displayed.

Allow reuse

Allows the reuse of one data item as an attribute for more than one entity provided the attributes have same name and data type and do not belong to a primary key.

When deselected or when the attribute belongs to a primary key, the data item cannot be reused. In this case, if the Unique code check box is selected, a new data item with identical name but different code is created, otherwise a new data item with identical name and code is created.

When you delete an entity or entity attributes, these options determine whether or not the corresponding data items are also deleted, as follows:

  • Both – deletes the entity attribute.

  • Unique Code only – deletes the entity attribute.

  • Allow Reuse only – deletes the entity attribute and the corresponding data item (if it is not used by another entity).

  • None – deletes the entity attribute and the corresponding data item.

For information about controlling the naming conventions of your models, see Core Features Guide > Modeling with PowerDesigner > Objects > Naming Conventions.