Show TOC

Post-ImportLocate this document in the navigation structure

You should perform a certain number of checks after import, and also be prepared for certain differences in your models.

We recommend that you perform the following post-import checks:
  • Import triggers - Triggers cannot be directly imported from ERwin. There are, however, two methods for transferring your constraint trigger information to PowerDesigner:

    • Automatically generate triggers - Select Start of the navigation path Tools Next navigation step Rebuild Objects Next navigation step Rebuild Triggers End of the navigation path. Creating triggers in this way ensures that they will be synchronized automatically by PowerDesigner, but the actual code may be different from that which you are used to in ERwin.

    • Reverse engineer triggers - Generate the triggers from ERwin, and then reverse engineer them into PowerDesigner. Creating triggers in this way ensures that they use exactly the same code as before, but they will not be automatically synchronized by PowerDesigner.

  • Import procedures: Procedures cannot be directly imported from ERwin. You can, however transfer them by generating the triggers from ERwin, and then reverse engineering them into PowerDesigner.

  • Set up object naming conventions - Select Start of the navigation path Tools Next navigation step Model Options End of the navigation path, expand the Naming Convention category and select the object entry (see Core Features Guide > Modeling with PowerDesigner > Objects > Naming Conventions).

  • Select other model options - Select Start of the navigation path Tools Next navigation step Model Options End of the navigation path, and select the Model Settings category or one of its children (see Setting CDM/LDM Model Options and Setting PDM Model Options)
The following are some differences that are commonly encountered when working with a newly imported ERwin model:

  • Why do I see errors in Check Model when my ERwin model was clean? - PowerDesigner performs stricter checks than ERwin. For example, duplicate objects are not permitted in PowerDesigner, and the existence of orphaned items will generate a warning.

  • Why do some of my object symbols appear with numeric suffixes? - If an object is required to appear more than once in a diagram (for, example, to improve readability), PowerDesigner will create a graphical synonym to represent it. Thus, if the table "Purchase" is displayed twice in a diagram, the two symbols will be labeled as "Purchase: 1" and "Purchase: 2".