Validation Process

As has been described in Comparison and Merging Processes there are two validation checks you can perform prior to the full import and merging of models.

The first option is for profile mapping. The Profile Mapping? Option on the Run Information window turns this on. The Import process initializes normally and calls the external program to process the incoming file. In so doing it checks for a complete mapping of the profiles in the mapping tables. A log file is produced. No further Import actions are undertaken with this option.

Second, you can check that there are not any duplicate UUIDs. This can quite easily come about if you copy members in AVEVA Bocad Steel without creating unique UUIDs for them. When they are imported into the base product, the Comparison process may fail as it could be uncertain as to which member it is supposed to be comparing.

The options for this check are NEW and GLOBAL. NONE turns the facility off. NEW checks among all this run's imported members contained in the reference model for duplicate UUIDs, while GLOBAL checks the whole structural database, both imported and existing elements. These can be quite slow options as the reference model must be created and compared anyway.

As this option also calls the external program which checks the mapping of profile names between systems, you will see that the log file may also list any problems with the mapping tables. So this option is actually a combination of this and the previously mentioned validity checking option. For a sample log file, refer to Sample Validity Check Log File for further information.