is only supported on Microsoft Windows.
|Tool Name||PowerDesigner LDM (Logical Data Modeling)|
|Tool Version||15.x to 16.x|
|Tool Web Site||https://www.sap.com/products/powerdesigner-data-modeling-tools.html|
|Supported Methodology||[Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing), Graphical Layout via LDM XML File|
|Remote Repository Browsing for Model Selection|
Import tool: SAP PowerDesigner LDM (Logical Data Modeling) 15.x to 16.x (https://www.sap.com/products/powerdesigner-data-modeling-tools.html)
Import interface: [Data Modeling] Data Store (Physical Data Model, Stored Procedure Expression Parsing), Graphical Layout via LDM XML File from SAP PowerDesigner LDM 15.x to 16.x Import bridge: 'SybasePowerDesignerLdm15' 10.1.0
This bridge imports a Logical Data Model from an LDM XML file.
LDM files in binary format are not supported.
FREQUENTLY ASKED QUESTIONS
Q: How do I handle LDM XML files which contain shortcuts to external entities?
A: LDM XML model files may contain relationships which refer to entities defined as shortcuts, which are references to external entities. Unfortunately, in this case the LDM XML file does not contain sufficient information to reconstruct the PK/FK relationships properly. If this is the case with the imported file, there will be a message in the log like:
This model may have shortcut dependencies on external model: 'file:///...'
and, by default, the bridge will not attempt to reconstruct those PK/FK relationships to shortcuts.
However, the source tool has the capability to merge these files together so that the shortcuts are resolved. To do so:
- Refer to the log for all the files with shortcuts
- Open the tool and go to the Tools -> Merge Models... menu option
- Create a new merged model
- Save the new model as a LDM XML and import.
Q: I see warnings or errors in the log, How can I validate the model before importing?
A: PowerDesigner allows checking the model for modeling inconsistencies.
Please use menu Tools -> Check Model... and take necessary corrective actions to resolve detected issues.
|File||This bridge imports LDM XML files. If you do not have the model saved as a LDM XML file already, you may create a LDM file for import:
1. Be sure the logical data model is opened in Sybase PowerDesigner.
2. Choose 'Save As' from the 'File' menu.
3. In the 'Save as type' list, select 'Logical Data Model (xml) (*.ldm)'.
4. In the File Name text box, enter the file name and select a directory to save the file in.
5. Click 'Save'.
The bridge will use the generated LDM XML file as input.
|Apply binary characters filter||Specifies if invalid binary characters should be filtered out of the file as a pre-process, before parsing the LDM XML file. This option is a workaround for a bug in the PowerDesigner tool which sometimes generates a file that is not conformant with the XML specification, with binary characters in it.
Warning: applying this filter may remove some Unicode national characters.
If it does removes some of your Unicode national characters, you may try to turn this option off.
True is the default.
|Import UDPs||A User Defined Property (UDP) is usually defined with a property definition object that has a default value. The objects the property applies to may also specify an explicit value for this property, or no value at all in which case the default value of the property definition applies.
This option allows you to control how property definitions and values are imported:
By default, the bridge imports the property definition as a Property Type.
'As metadata' - Import an explicit value as Property Value, implicit values are not imported, the default value is kept on the Property Type only. This is the default behavior.
'As metadata, migrate default values' - Import explicit and implicit values as Property Value objects.
'In description, migrate default values' - Append the property name and value, even if implicit, to the object's description property only. This allows you to export the UDP values to another tool which does not support the notion of UDP.
'Both, migrate default values' - Import the UDP value, even if implicit, both as metadata and in the object's description.
|Append volumetric information to the description field||Import and append the volumetric (number of occurrences) information to the description property.||BOOLEAN||False|
|Remove text formatting||Select to remove Rich Text Formatting (RTF) from annotations. PowerDesigner stores annotations as plain text or Rich Text Formatting (RTF).
Set this option to 'False' :
- or if your target tool is capable of displaying RTF text
Set this option to 'True' :
- and your target tool is not capable of displaying RTF text
|Reverse role names||This option tells the bridge to swap the rolenames for each relationship in the model.
'False' - Do not reverse rolenames. This is the default.
'True' - Reverse rolenames.
Mapping information is not available