Data Item Checks (CDM)

PowerDesigner provides default model checks to verify the validity of data items.

Check

Description and Correction

Data item name and code uniqueness

Data item names and codes must be unique in the model.

Manual correction: Modify the duplicate name/code

Automatic correction: Appends a number to the duplicate name/code.

Data item not used

There are unused data items. These are useless for PDM generation.

Manual correction: To use a data item, add it to an entity. If you do not need an unused data item, delete it to allow PDM generation.

Automatic correction: None.

Data item used multiple times

There are entities using the same data items. This can be tolerated if you defined this check as a warning.

Manual correction: Take care to ensure consistency when defining data item properties.

Automatic correction: None.

Detect differences between data item and associated domain

There is a divergence between data items and associated domains. This can be tolerated if you defined this check as a warning.

Manual correction: Ensure consistency when defining data item properties

Automatic correction: Restores divergent attributes from domain to data items (domain values overwrite data item values).

Detect inconsistencies between check parameters

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

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

Undefined data types for data items exist. To be complete, a model should have all its data items 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

Invalid data types for data items exist. To be complete, a model should have all its data types for data items 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.