Entity Attribute Checks (CDM/LDM)

PowerDesigner provides default model checks to verify the validity of entity attributes.

Check	Description and Correction
Name/Code contains terms not in glossary	[if glossary enabled] Names and codes must contain only approved terms drawn from the glossary. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - None.
Name/Code contains synonyms of glossary terms	[if glossary enabled] Names and codes must not contain synonyms of glossary terms. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - Replaces synonyms with their associated glossary terms.
Name/Code uniqueness	Object names must be unique in the namespace. Manual correction - Modify the duplicate name or code. Automatic correction - Appends a number to the duplicate name or code.
Detect differences between attribute and associated domain	[LDM only] There is a divergence between attributes and associated domains. This can be tolerated if you defined this check as a warning. Manual correction: Ensure consistency when defining attribute properties Automatic correction: Restores divergent attributes from domain to attributes (domain values overwrite attribute values).
Detect inconsistencies between check parameters	[LDM only] The values entered in the Check Parameters page are inconsistent for numeric and string data types. Default does not respect minimum and maximum values, or default does not belong to list of values, or values in list are not included in minimum and maximum values, or minimum is greater than maximum value. Check parameters must be defined consistently. Manual correction: Modify default, minimum, maximum or list of values in the check parameters page Automatic correction: None.
Precision > maximum length	[LDM only] The data type precision should not be greater than or equal to the length. Manual correction: Make the data type length greater than or equal to the precision. Automatic correction: None.
Undefined data type	[LDM only] Undefined data types for attributes exist. To be complete, a model should have all its attributes data types defined. Manual correction: While undefined data types are tolerated, you must select data types for currently undefined data types before you can generate a PDM. Automatic correction: None.
Invalid data type	[LDM only] Invalid data types for attributes exist. To be complete, a model should have all its data types for attributes correctly defined. Manual correction: While tolerated, you must select valid data types for currently non-valid data types to generate the PDM. Automatic correction: None.