Rules for Uploading and Checking In Design Table Objects (CATIA V5)
Consider these rules for using Upload and Check In with design table objects:
• To check in changes that you made to the design table, you must first save it to the workspace by saving the generic CATIA V5 model to the workspace.
• When you check in a modified member of a design table, you must check in the generic and all instances. If
independently.modify.instances is set to Yes, then only modified instances are checked in. See
Modifying Instance Files Independently for more information.
• New instances are collected and included on checkin.
• Instances deleted from the design table when editing the generic are collected and removed from the workspace upon checkin.
• A design table file is required for checking in the generic.
• Attempting to upload or check in any design table member that is not checked out results in a conflict. You are provided with several choices to resolve the conflict so you can continue the upload or checkin process.
• If you Save to Workspace and Upload in CATIA V5, but Checkin to Windchill, you may have problems updating metadata if you use the auto-numbering feature and check out large objects on the fly. To avoid this, perform a Save to Workspace, Upload, and Checkin all in CATIA V5.