Show TOC

Reference and View Reference Checks (PDM)Locate this document in the navigation structure

PowerDesigner provides default model checks to verify the validity of references and view references.

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.

Reflexive and mandatory reference

[references only] A reflexive reference exists should not have a mandatory parent which could lead to inconsistent joins.

  • Manual correction: Correct the reference by clearing the Mandatory parent check box

  • Automatic correction: None

Existence of reference join

A reference must have at least one reference join.

  • Manual correction: Create a reference join for the reference or delete the reference

  • Automatic correction: Deletes reference without join

Reference code maximum length

[references only] The reference code length is limited by the maximum length specified in the DBMS definition (MaxConstLen entry, in the Start of the navigation path Object Next navigation step Reference End of the navigation path category) or in the naming conventions of the model options.

  • Manual correction: Modify the reference code length to meet this requirement

  • Automatic correction: Truncates the reference code length to the maximum length specified in the DBMS definition

Incomplete join

[references only] Joins must be complete.

  • Manual correction: Select a foreign key column or activate the primary key column migration

  • Automatic correction: None

Join order

[references only] The join order must be the same as the key column order for some DBMS.

  • Manual correction: If required, change the join order to reflect the key column order

  • Automatic correction: The join order is changed to match the key column order