Import Data Model Entities from Excel

Use the Files to import into Conceptual Model window to navigate to and then select the data model entities import file. Select Data Model (*.xlsx) from the Supported files drop down list.

Use the Data Model Import window to specify the entities to be imported.

Select the required worksheets for import.

Note:
Measure Class and UOM worksheets are defined in Dabacon and cannot be imported.

The Importing and Processing Selected Files window displays the progress of the import, by default the Show Details pane is collapsed.

Cells with a grey background in the import file are reference only and subject to validation rules during import which vary for each type of entity.

The following validation rules are applicable to data model entities during import to the conceptual model.

Class

• Display Name is required and must be unique.

• If a Requirement is specified, it must exist in the model.

Attribute

• Display Name is required and must be unique.

• If a Data Type is specified, it must exist in the model.

• If a Unit is specified, it must exist as a valid UOM on a Data Type which is a Measure Class.

• If Length is specified, it must be a positive whole number or "*".

• If a Discipline is specified, it must exist in the model.

• An attribute cannot be both a Tag and a Language Variable.

• If set as a Tag, DataType must be set as "String", Discipline must not be set, and Is Pseudo must not be set.

• If set as a Language Variable, DataType must be set as "String".

• If a Valid Values List is specified, it must exist as a List of Values in the model.

• If a Valid Values List is specified, any specified Default Value must exist as a List of Values Item on the List of Values.

• If Minimum and Maximum are set, Maximum must be equal to or greater than Minimum.

• If a Requirement is specified, it must exist in the model.

Association

• Display Name must be unique.

Class Association

• Display Name must be unique.

• If a Discipline is specified, it must exist in the model.

• If Cardinality is specified, it must be a positive whole number or "*".

LOV

• Display Name is required and must be unique.

• Data Type is required and must exist in the model.

LOV Items

• LOV URI is required and must exist as the URI of a LOV in the model (refer to LOV worksheet).

• Display Name is required and must be unique.

• Value in most cases will match Display Name. This is the value which will be created in Dabacon.

Discipline

• Display Name is required and must be unique.

Identity

• Entity URI must exist as a valid URI of one of the following entity types:

  • Class

  • Attribute

  • Association

  • Class Association

  • LOV

  • LOV Item

  • Measure Class

  • UOM.

• Identity Version URI must exist as the URI of an Identity Version.

  Note:
  In addition to the above (and unlike other imports), if the value of an existing Identity is set to blank, the Identity is deleted on import. All the other types of import only create or update entities, they are not deleted.

Relationships

The following types of relationship can be created:

1. Class to Class (Class Hierarchy)

   1. Domain and Domain URI must exist as a valid Class. This will represent the child class.

   2. Association must be set as "Sub Class Of".

   3. Range and Range URI must exist as a valid Class. This will represent the parent class.

2. Class to Attribute

   4. Domain and Domain URI must exist as a valid Class.

   5. Association must be set as "Can Have As Attribute".

   6. Range and Range URI must exist as a valid Attribute.

3. Class to Class via Class Association

   7. Domain and Domain URI must exist as a valid Class. This will represent the source class.

   8. Association and Association URI must exist as a valid Class Association.

   9. Range and Range URI must exist as a valid Class. This will represent the target class.