SmarTeam - SolidWorks Integration

General Issues

Performance It takes a long time to open SolidWorks Parts that contain many in-context relations.
Preview Conversion on the fly
The SolidWorks Conversion on the fly mechanism does not work properly when the user selects the 'No preview during open (faster)' option from the SolidWorks options > Performance section.
Refresh The Refresh option does not work in the Profile Card and you must close and then re-open the profile card to update the display.
General When a simplified extension character appears in a configuration name multiple times, the simplified configuration may be saved to SmarTeam more than once.
Simplified Configurations In some cases, when using simplified configurations, the master configuration is not updated in SmarTeam when you rename the configuration. Therefore, it is recommended that you update the master configuration in SmarTeam.
Bulk Load

In some cases, after performing a Bulk Load operation on a SolidWorks assembly with multiple configurations, hierarchical links are not created and the assembly structure is incorrect.

As a result, it is recommended that you open the assembly in SolidWorks and save it to SmarTeam.

Links The newly created component does not appear in the relevant SolidWorks assembly when you use the following SolidWorks functionalities:
  • Insert a new component to a SolidWorks assembly when the SolidWorks option Save new components to external files is selected
  • Using Form a new subassembly from here

Open Issues

General  If you hide one of multiple instances of the same component in the Feature Manager Tree (FMT), all components are shown as hidden in the Data Manager Tree (DMT).
  Workaround:
  None
Lifecycle SolidWorks properties are not updated when checking out a read-only file.
  Workaround:
  None
Toolbox Smart Fasteners inserted into an assembly are not automatically released for a Toolbox part.
  Workaround:
  Populate toolbox parts and release them to SmarTeam.
Conversion on Demand

SmarTeam File Converter converts files from an earlier release of SolidWorks to the current release. This conversion optimizes the files for the latest SolidWorks enhancements and eliminates file conversion during SmarTeam - SolidWorks design.

The conversion process can be applied to files which reside in SmarTeam vaults. SmarTeam File Converter, which can be run in interactive mode or in silent mode, does not modify file content or SmarTeam objects, so the files remain in the same revision as before conversion. Conversion can be run for files which reside in the local vault only. The administrator must run the conversion on each side for its local vaults.


Important: When deploying a new SolidWorks version, it is recommended to convert vaulted files to the current SolidWorks version.


Notes:
  1. Before running SmarTeam File Converter, it is strongly recommended to perform a backup of the vault. After the conversion, it is recommended to verify that files were converted correctly.
  2. Close all documents opened in SolidWorks before launching migration process

Using the SmarTeam File Convertor Utility

The administrator must define predefined queries. It is recommended to define separate queries for Parts, Assemblies and Drawings and to run the conversion process in this order: Parts, Assemblies and then Drawings.

For more information, refer to SmarTeam - Editor Online Help > Administration and Configuration > SmarTeam File Converter.

Using Script

The administrator can assign a script for User Defined Tools in SmarTeam Script Maintenance. This tool can convert files by selecting corresponding objects in SmarTeam - Editor, so the user will be able to convert files to current SolidWorks version on demand by selecting the object.

A sample script,  ConversionOnDemand.ebs, is provided in the SolidWorks script directory. 

The ConversionOnDemand.ebs Log file is located in:


Vista and Windows 7:

%ProgramData%\SmarTeam\SmarTeam File Converter

Windows XP:
%ALLUSERSPROFILE%\Application Data\SmarTeam\SmarTeam File Converter

This directory is created automatically the first time you launch the SmarTeam File Convertor utility.
If you choose to use the script, create the directory manually.

Lifecycle A SolidWorks document (part/assembly/drawing) from an older version is not identified in the Data Manager Tree when using the Replace previous revision lifecycle option.
  Workaround:
  None
Insert Component When you use 'New assembly' option from 'Insert component' command, and the SW option 'Save new component to external files' is selected', an error message appears. The component is inserted into the assembly, but the SolidWorks Save option appears instead of the SmarTeam Save option.
  Workaround:
  None
Links A link is not created between a split body and the original part when you perform a SmarTeam Save operation on the split body.
  Workaround:
  None
Lifecycle When separate checkout operations are performed on objects in a single structure, Microsoft .NET framework error messages may be displayed while clicking on object nodes in the Data Manager Tree (DMT).
  Workaround:
  None
Documentation When you save a SolidWorks part/assembly with multiple configurations, a profile card is displayed for each configuration. The first profile card displays the default class. If the user selects a class other than the default class, the other profile cards will display the selected class.
  Workaround:
  None
General An unhandled exception error is displayed when using the Data Manager Tree > Go To option for an unsaved document.
  Workaround:
  None
Configurations Configuration
User cannot add a configuration to a vaulted object.
  Workaround:
  To add a configuration, the object should be checked out.
Virtual components SolidWorks assemblies that contain virtual components cannot be duplicated using Design Copy.
  Workaround:
  To perform a Design Copy operation, the user must externalize all virtual components prior to performing the Design Copy operation. Performing Design Copy with virtual components may cause broken links within the SolidWorks assembly.
Insert Component When you perform an Insert Component operation from the SmarTeam menu on a read-only assembly in SolidWorks, the Check Out on the Fly notification is not displayed. As a result, the user may insert the component into the assembly, but a subsequent Save operation will fail because the assembly is read-only.
  Workaround:
  To save the changes made to the assembly, select the SmarTeam Overwrite Open Dialog option and use the SolidWorks Insert Component option.
Detached Drawing When working in the SmarTeam - SolidWorks integration, the model is not found when you open a vaulted detached drawing using Load Model.
  Workaround:
  None
Save Operation A Save operation cannot be performed if the same part appears in different levels in the structure with a virtual component.
  Workaround:
  None
Open Dialog The "Do not load hidden" option in the Open Dialog is ignored if the "Open for edit" check box is marked.
  Workaround:
  When using the "Open for" option, everything works correctly.
Mapping  Mass properties for an assembly are not mapped to the Profile Card.
Note: Mapping of mass properties for parts is successful.
Simplified Configurations If a simplified extension appears more than once, the configuration name of a simplified configuration in SmarTeam will include the simplified extension.
  Workaround:
  Use a simplified extension only once.
Design Table If you add Design Table to a checked in document in SolidWorks and check out the document [modification notification appears] and check in the document, the document loses the Design Table.
  Workaround:
  Check out the document and then add the Design Table.

Documentation

None