Import Process

After clicking OK the fields in the window are checked for validity:

• Is the storage location valid?

• Is there a valid input file?

• Do we need to convert the file across platforms?

• Are the Profile and Material mapping files valid?

After verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. This waiting time is user configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or not even exist. You will be asked if want to carry on waiting for another time unit.

Click Yes and the interface will wait for another period of time. Click No causes the interface to stop where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated.

You will be alerted to unsuccessful runs by the external program displaying an Error window, after which the process exits.

If the external program successfully completes, the processed file will be imported into the design model. Any reference data which may have been retained by you before will have been deleted beforehand.

The status line will inform you of the progress on importing the data, the length of the input macro is about 25 times the number of elements. Thus a file transferring 300 members is about 7500 lines long. This calculation can be useful when considering the maximum input file size. The size applies to this file and not to the original SDNF source file.

After the Import of everything, the material properties are reconciled with the :FABMGRADE attribute and, if possible, the MATR is also set to point to the appropriate property in the Properties database.

At this point, if you have chosen to be asked whether to Merge after the Compare operation, Confirm window is displayed.

Click Yes and the interface continues with the Merge process.

Click No and the Import process skips the Merging, but you are then given a chance to store the Merging commands in a file for use later on only in the current base product session. You cannot use a file from a previous session as the Import data may be incorrect.

You can save the Merge command file and then be prompted whether to see the Import log file. This Merge command file may then be used in the Merge from File option on the Import window. This latter option needs the reference model from this run to be kept. Therefore, you do not have the option below.

If you have merged the models, they will then be asked if they want to keep the reference model, verifying the option selected on the Run Information window.

Note:

This reference model will not be the complete model as imported as various attributes and elements might have been modified, deleted or moved around.

Finally, you are asked whether to view the log file, if they have chosen that option on the Run Information window.

If you want to inspect the log file, they can then save it with the File > Save as option in the File Viewer window which will bring up a File Browser, or by clicking Save as to the suggested filename. If the file exists, you will be asked whether they want to overwrite it. The log file window can then be closed by clicking Cancel.

If you have chosen Brief mode on the Run Information window for displaying the log file, the window displaying the log file will filter out all Warning messages, leaving only the Error messages. To save the log file, however, all messages will be retained in the file.

Clicking on a line containing a base product reference number causes all graphical views to zoom in to the chosen item and to identify it. The interface also navigates to the item in the database and leave you there to perform any queries or operations.