Save to Workspace (NX)
The Save to Workspace command allows you to save the active file and all its references from the local file system to the active workspace. In NX, click > to access this command. This command is available only if you have opened an NX file from the local file system. To save multiple NX files (and larger data sets) in one operation, use the Import to Workspace command in the Windchill Workgroup Manager client user interface.
 |
• If you insert a model that does not exist in your workspace into an existing assembly, a warning message appears. To resolve this, save the model to the workspace.
• The publishing of NX data with multi-byte filename and attribute characters is supported with UTF-8 encoding. For more information, see the article.
|
Save to Workspace locates an object in the last saved location. You can also browse to other locations.
You can control the revision of a new document using Save To Workspace. The preference InitialRevisionParameter identifies the file property name that shows the initial revision to be used when uploading a file to Windchill. This revision can only be set while performing the first save. Any further revisions are controlled by Windchill. The Revision System Attributepreference identifies the name of the property in the CAD tool that shows the CAD documents revision.
|
|
You can save the NX models using multi-byte characters in file name and file path.
|
Handling of References to Files outside the Workspace
Whenever a CAD part or assembly from the local system is inserted into an existing assembly, a warning message appears, indicating that one or more files are being referenced from outside the workspace, and that those files must be imported to the workspace. The Windchill Workgroup Manager message area lists the components referenced from outside the workspace. Missing dependents are created for the referenced components and treated like ghost objects. You need to import the referenced components to resolve them.
Save to Workspace of Independent Family Tables in NX
• When the server preference Independently Modify Instances is set to Yes (default) for NX, you can save the standalone generic to the workspace, but its instances are not saved in your workspace.
• When the server preference Independently Modify Instances is set to No for NX, you can save the standalone generic to the workspace. Once the generic is saved to Windchill, its instances are also saved in your workspace.
Best Practices while Saving NX Files to Windchill
• In the Assembly Load Options window, avoid adding three dots at the end of the search path if you do not want to search the files in subolders.
• Setting expose.model.annotation preference to Designated updates only selected Product Manufacturing Information (PMI) to Windchill, which saves the assembly faster.
• When saving a large assembly with many family table instances, set the Independently Modify Instances preference to Yes to save only the standalone generic to the workspace. This setting uses fewer resources and speeds up the saving process.
• Setting the Independently Modify Instances preference to No slows down the saving process, as it saves both the standalone generic and the instance.
|
|
NX does not support the creation of client-side viewables when you use Save to Workspace.
|