About Adding Designs to the 3DEXPERIENCE Server

There are multiple ways to add designs and other files (for example, pdf, jpg, png, and more) to the server.

This page discusses:

You can use:

  • The SOLIDWORKS File > Save As commands to save files to an existing folder in a 3DEXPERIENCE local directory.
    Note: This is the only option for first time check-in of a derived PDF file that you create by saving in SOLIDWORKS a file as a .pdf file.
  • Standard Windows procedures like drag and drop or copy and paste to add files to a workspace folder.

With either method, you must check the files into the server to share them, along with their design information, across the enterprise. Design information consists of the physical files created in SOLIDWORKS plus metadata or descriptive characteristics. Save the designs often to keep the collaborative group informed of any changes.

When doing a first-time check-in of an assembly, the Check In dialog box requires you to check in simultaneously all the reference files for the assembly. For subsequent check-ins, the requirement to include reference files in the check-in depends on the administrator setting of the Global Configuration Object (GCO) attributes, SLW-CheckInPermitIncomplete and SLW-CheckInBlockRemoteReferences.

  • SLW-CheckInPermitIncomplete - This GCO controls the check-in of reference files that are located in the 3DEXPERIENCE local directory. When the administrator sets the GCO to TRUE (the default), you can choose whether or not to include the reference files. When the GCO is set to FALSE, the check-in only completes if you include the checked out reference files.
  • SLW-CheckInBlockRemoteReferences - This GCO controls the check-in of reference files that are outside of the 3DEXPERIENCE local directory. When the administrator sets this GCO to TRUE (the default), the checked out reference files outside of the local directory, are noted with a warning. When the GCO is set to FALSE, the check-in only completes if you include the checked out reference files.

Important: To save a file to the server, the combination of the file name and configuration name cannot exceed 127 characters.

Attribute Synchronization

Attribute synchronization occurs automatically when you check out files. It ensures that the attributes in the design file on your computer match the attributes of the associated server object.

Check Out Status of Designs

Checking out designs from the server ensures that no other user can modify the designs on which you are working. Check out status of a design indicates whether you or any other user has checked out the design that exists on the server. You can edit only those designs on the server that are checked out by you and not another user.

Tip: Check out status is valid only for designs that exist on the 3DEXPERIENCE server. Consequently, it is not displayed when you check in designs for the first time.

Checking out a file indicates the intent to modify the file.

You can also use the Keep Checked Out option when checking in designs. By selecting this option during a check-in, you can ensure the checked out status is maintained so that you can perform subsequent edits and saves.

New Revision Streams

A revision is a controlled release of a design that replaces previous releases. Each release is usually identified by revision. Revisioning maintains the history of a design so that you can return to a previous release at any time.

To create a new revision stream when you check in a design, check the Increment Revision option in the Check In dialog box. The new revision stream is next in sequence to the current stream.

See Incrementing Revisions for Checked Out Files.

You can also increment revisions on files that are not checked out.

See Incrementing Revisions for Files That Are Not Checked Out

Obsolete

A design is considered obsolete if a newer design exists on the server. The Check In and Check Out dialog boxes, as well as the File Explorer window and the 3DEXPERIENCE task pane all indicate the revision and iteration existing in the local cache with the format A.1/B.1. In this case, the A.1 on the left side indicates the revision and iteration number of the file in the local cache. The B.1 on the right side indicates the revision and iteration of the file on the server.