Copy model/drawing and replace all references
Create an independent copy without leaving drawings or assemblies linked to the old model unintentionally. Work on a copy first. Record application version, units and active document/configuration. Names below identify the catalogued workflow; they do not claim a particular button layout or verified implementation.
Copy the reference graph, not just filenames
OPEN FULL SIZE ↗- Map
- Explicit old to new
- Include
- Required dependent files
- Test
- Originals unavailable in a test location
TECHNICAL NOTES///
Create an independent copy without leaving drawings or assemblies linked to the old model unintentionally.
GOALRun the first test described in this guide and record the result for copy model/drawing and replace all references.
PREPARATION / NOTES
Work on a copy first. Record application version, units and active document/configuration. Names below identify the catalogued workflow; they do not claim a particular button layout or verified implementation.
EQUIPMENT
- CAD / automation tool
- Representative test model
- Measurement or inspection method
STEPS
- Build a dependency list and choose destination filenames with collision handling.
- Use the application’s supported copy/reference workflow and include all required dependent files.
- Replace references using an explicit old-to-new map, preserving configurations and relative relationships.
- Open the copied top-level model and drawing with the originals unavailable in a test location, then rebuild and inspect references.
TROUBLESHOOTING
- Renaming a file in Explorer is not a complete reference update. Shared purchased components may intentionally remain shared; define that policy first.
THINGS TO WATCH FOR
Renaming a file in Explorer is not a complete reference update. Shared purchased components may intentionally remain shared; define that policy first.
RESULTThe copied project resolves only to the intended new or explicitly shared files.
DEVELOPMENT HISTORY///
Imported as an independent manifest record; public copy keeps uncertainty visible.
SPECIFICATION///
RELEASED MATERIAL///
The copied project resolves only to the intended new or explicitly shared files.
The record keeps what is known at this revision. Unfinished tests stay unfinished here.