Logical Data Object Model Properties

Property	Description
Import UDPs	Specifies how to import user-defined properties. Select one of the following options: - As metadata. Import an explicit value as the property value object. Explicit values are not exported. - 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 description property. - Both, migrate default values. Import the UDP value, even if implicit, both as metadata and in the object's description. Default is As metadata.
Import relationship name	Specifies how to import the relationship names from ERwin. Select one of the following options: - From relationship name - From relationship description Default is From relationship name.
Import IDs	Specifies whether to set the unique ID of the object as the NativeId property.
Import subject areas	Specifies how to import the subject areas from ERwin. Select one of the following options: - As diagrams - As packages and diagrams - As packages and diagrams, assuming one subject area for each entity - Do not import subject areas Default is As diagrams.
Import column order form	Specifies how to import the position of columns in tables. Select one of the following options: - Column order. Order of the columns displayed in the ERwin physical view. - Physical order. Order of the columns in the database, as generated in the SQL DDL. Default is Physical order.
Import owner schemas	Specifies whether to import owner schemas.

IBM Cognos Business Intelligence Reporting - Framework Manager Import Properties

Property	Description
Folder Representation	Specifies how to represent folders from the Framework Manager. Select one of the following options: - Ignore. Ignore folders. - Flat. Represent folders as diagrams but do not preserve hierarchy. - Hierarchial. Represent folders as diagrams and preserve hierarchy. Default is Ignore.
Package Representation	Specifies how to represent packages from Cognos Framework Manager. Select one of the following options: - Ignore. Ignore subject areas. - Subject Areas. Represent packages as subject areas. - Model. Represent the package as the model. Default is Ignore.
Reverse engineer relationships	Specifes whether the Developer tool computes the relationship between two dbQueries as referential integrity constraints.
Tables design level	Specifies how to control the design level of the imported tables: Select one of the following options: - Logical and physical. The tables appear in both the logical view and in the physical view of the model. - Physical. The tables appear only in the physical view of the model. Default is Physical.
Ignore usage property	Specify whether the usage property of a queryItem should be used.

SAP BusinessObjects Designer Import Properties

Property	Description
System	Name of the BusinessObjects repository. For BusinessObjects versions 11.x and 12.x (XI), enter the name of the Central Management Server. For BusinessObjects version 5.x and 6.x, enter name of the repository defined by the Supervisor application
Authentication mode	Login authentication mode. This parameter is applicable to SAP BusinessObjects Designer 11.0 and later. Select one of the following authentication modes: - Enterprise. Business Objects Enterprise login - LDAP. LDAP server authentication - Windows AD. Windows Active Directory server authentication - Windows NT. Windows NT domain server authentication - Standalone. Standalone authentication Default is Enterprise.
User name	User name in the BusinessObjects server. For version 11.x and 12.x (XI), you need to be a member of BusinessObjects groups.
Password	Password for the BusinessObjects server.
Silent execution	Specifies whether to execute in interactive or silent mode. Default is Silent.
Close after execution	Specify whether to close BusinessObjects after the Developer Tool completes the model import.
Table design level	Specifies the design level of the imported tables. Select one of the following options: - Logical and physical. The tables appear both in the logical view and in the physical view of the model. - Physical. The tables appear both in the physical view of the model. Default is Physical.
Transform Joins to Foreign Keys	Transforms simple SQL joins in the model into foreign key relationships. Select the parameter if you want to export the model to a tool that only supports structural relational metadata, such as a database design tool.
Class representation	Specifies how to import the tree structure of classes and sub-classes. The Developer Tool imports each class as a dimension as defined by the CWM OLAP standard. The Developer Tool also imports classes and sub-classes as a tree of packages as defined by the CWM and UML standards. Select one of the following options: - As a flat structure. The Developer tool does not create package. - As a simplified tree structure. The Developer tool creates package for each class with sub-classes. - As a full tree structure. The Developer tool creates a package for each class. Default is As a flat structure.
Include List of Values	Controls how the Developer tool imports the list of values associated with objects.
Dimensional properties transformation	Specifies how to transfer the dimension name, description, and role to the underlying table and the attribute name, description, and datatype to the underlying column. Select one of the following options: - Disabled. No property transfer occurs. - Enabled. Property transfer occurs where there are direct matches between the dimensional objects and the relational objects. The Developer tool migrates the dimension names to the relational names. - Enabled (preserve names). Property transfer occurs where there are direct matches between the dimensional objects and the relational objects. The Developer tool preserves the relational names. Default is Disabled.

SAP PowerDesigner CDM Import Properties

Property	Description
Import UDPs	Specifies how to import user-defined properties. Select one of the following options: - As metadata. Import an explicit value as the property value object. Explicit values are not exported. - 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 description property. - Both, migrate default values. Import the UDP value, even if implicit, both as metadata and in the object's description. Default is As metadata.
Import Association Classes	Specifies whether the Developer tool should import association classes.
Import IDs	Specifies whether to set the unique ID of the object as the NativeId property.
Append volumetric information to the description field	Import and append the number of occurrences information to the description property.
Remove text formatting	Specifies whether to remove or keep rich text formatting. Select this option if the model was generated by PowerDesigner 7.0 or 7.5 Clear this option if the model was generated by PowerDesigner 8.0 or greater.

SAP PowerDesigner OOM 9.x to 15.x Import Properties

Property	Description
Target Tool	Specifies which tool generated the model you want to import. Select one of the following options: - Auto Detect. The Developer tool detects which tool generated the file. - OMG XMI. The file conforms to the OMG XMI 1.0 standard DTDs. - Argo/UML 0.7. The file was generated by Argo/UML 0.7.0 or earlier. - Argo/UML 0.8. The file was generated by Argo/UML 0.7.1 or later. - XMI Toolkit. The file was generated by IBM XMI Toolkit. - XMI Interchange. The file was generated by Unisys Rose XMI Interchange. - Rose UML. The file was generated by Unisys Rose UML. - Visio UML. The file was generated by Microsoft Visio Professional 2002 and Visio for Enterprise Architects using UML to XMI Export. - PowerDesigner UML. The file was generated by Sybase PowerDesigner using XMI Export. - Component Modeler. The file was generated by CA AllFusion Component Modeler using XMI Export. - Netbeans XMI Writer. The file was generated by one of applications using Netbeans XMI Writer such as Poseidon. - Embarcadero Describe. The file was generated by Embarcadero Describe. Default is Auto Detect.
Auto Correct	Fix and import an incomplete or incorrect model in the XML file.
Model Filter	Model to import if the XML file contains more than one model. Use a comma to separate multiple models.
Top Package	The top-level package in the model.
Import UUIDs	Import UUIDs as NativeId.

SAP PowerDesigner PDM Import Properties

Property	Description
Import UDPs	Specifies how to import user-defined properties. Select one of the following options: - As metadata. Import an explicit value as the property value object. Explicit values are not exported. - 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 description property. - Both, migrate default values. Import the UDP value, even if implicit, both as metadata and in the object's description. Default is As metadata.
Import IDs	Specifies whether to set the unique id of the object as the NativeId property.
Append volumetric information to the description field	Import and append the number of occurrences information to the description property.
Remove text formatting	Specifies whether to remove or keep rich text formatting. Select this option if the model was generated by PowerDesigner 7.0 or 7.5 Clear this option if the model was generated by PowerDesigner 8.0 or greater.

XSD Import Properties

Property	Description
Elements content name	Attribute to hold the textual content like #PCDATA in the XSD file. Default is As metadata.
Collapse Level	Specifies when to collapse a class. The value you select determines whether the Developer tool imports all or some of the elements and attributes in the XSD file. Select one of the following options: - None. Every XSD element becomes a class and every XSD attribute becomes an attribute. - Empty. Only empty classes collapse into the parent classes. - Single Attribute. Only XSD elements with a single attribute and no children collapse into the parent class. - No Children. Any XSD element that has no child element collapse into the parent class. - All. All collapsible XSD elements collapse into the parent class. Default is All.
Collapse Star	Specifies whether the Developer tool should collapase XML elements with an incoming xlink into the parent class.
Class Type	Specifies whether the Developer tool should create a class type an element collapses into the parent element.
Any	Specifies whether to create a class or entity for the 'xs:any' pseudo-element.
Generate IDs	Specifies whether to generate additional attributes to create primary and foreign keys. By default, the Developer tool does not generate additional attributes.
Import substitutionGroup as	Specifies how to represent inheritance. Select one of the following options: - Generalization. Represents inheritance as generalization. - Roll down. Duplicate inherited attributes in the subclass. Default is Roll down.
Include Path	Path to the directory that contains the included schema files, if any.
UDP namespace	Namespace that contains attributes to be imported as user-defined properties.