Excel Import Plugin 18.5 Documentation

Skip to end of metadata
Go to start of metadata

There are three methods to import data from table rows in an Excel or CSV file: 

(i) Import them as instance specifications of a schema class when importing the schema class. 

(ii) Import them as instance specifications of a schema class after importing the schema class. 

(iii) Import them through a class mapping. 

You can import instance specifications at the same time you import a schema class by using the Import Table Heading from Excel wizard. The wizard provides the check box, if you want to opt for this option. The first method helps you import table headings as schema classes and table rows as instance specifications of the schema classes simultaneously. The second method is a means of importing table rows as instance specifications to an already created schema class. 

The third method, importing data through a class mapping, means importing data from table rows from an Excel or CSV file according to the mapped target element type in the class mapping. 

The Import Data from Excel menu in the Import Data from Excel and Create Mapping dialog opens the Import Data from Excel wizard. This wizard helps you select a file from which you want to import instance specifications to a schema class or import data through a class mapping that you have created. 

If the name and the type of an imported element is the same as the name and the type of an existing element (include the inherited element type), the Excel Import plugin will use the imported one to overwrite and update the existing one only if they are in the same package or sub-package. 

When you import data through a class mapping, the result of import will be in accordance with the target element type of the class mapping. When mapping properties of a schema class and a target element, you can choose one out of three possible target elements: a UML profile, a SysML profile, or a user model. Therefore, if your class mapping has a user model as the target, the imported data will become instance specifications of the user model. However, if your class mapping has a UML or a SysML profile as the target, the imported data or elements will become a UML or a SysML element of the selected type. 

 

  • No labels