|
Even though the shared object remains hidden in the project, setting the Folder Contents table to display hidden objects does not make a shared object visible.
|
Before You Convert to PDM Checkout |
---|
Before converting a shared object to PDM checkout, you might need to take additional actions: • Ensure that the shared object is the latest iteration. Shared objects can continue to be modified from the PDM environment, meaning that the version you are viewing in a project might not reflect recent changes. You can only update objects that are out-of-sync with the sharing filter. Depending on the filter criteria, this might mean that you are unable to update the object to its latest iteration. If the iteration that exists in the project baseline is not the latest, the conversion to PDM checkout fails. A message appears asking you to update the object. In this situation, you can select Update from the right-click actions menu. From the Update Selected Shares window, edit the filter criteria to include the Latest configuration specification. For more information, see Update Selected Shares. • Verify whether the PDM checkout object affects any dependent or associated objects. Converting to PDM checkout is a single-object operation; no dependency processing takes place during the operation (meaning that you are not directed to the Collect Objects and Set Options table). To maintain structural integrity, you should consider checking out any dependent or associated objects as well. Use the Where Used table and any Related Objects tables available from the object information page to check for associated and dependent objects. • Ensure that you have the appropriate access. For more information, see Permissions and Valid Object Types. |