Improvements in Tekla Model Sharing

Tekla Structures 2019i introduces several improvements regarding Tekla Model Sharing. For example, reasons of write out failures are now stored in log files to simplify troubleshooting, and pour management is more robust than ever before.

Reasons of write out failures are stored in log files

If writing out model changes fails, the reasons for the failure are now saved in the error log and the model sharing log.

In the error_<user>_<YYYYMMDD>_<HHMMSS>.log file, you can find the reasons why Tekla Structures has failed to restore or save a file, or to write a material report export file or profile export file.

In the modelsharing.log file, you can find the reasons why creating data in the write out has failed. These errors can happen because of several reasons, such as low disk space, database errors, or using a user role that does not permit making certain changes.

Improved pour management

Pour management in shared models has been improved significantly. Unexpected conflicts have been addressed, so working with pour units is safer and more efficient than ever before.

Earlier, pour management could cause conflicts when reading in other users' changes, and as a result, objects in pour units might have been accidentally removed.

Improved and more robust sharing operations

Sharing operations now work more reliably even when other software are locking some of the files needed to perform the operations. For example, if a file that is needed to create a packet is opened by anti-virus software, Tekla Structures can still create the packet without errors.