Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Visualizing Documents And Their Contents And Links
colin_starker933
Member Posts: 16 EDU
I think I asked this before, but I can't remember and can't find it. I stepped away from a group project for a few months and came back to find things… in need of help. I need something like a tree (think Autodesk Vault) or flow chart with color coding for external document references. I searched for all objects of type = document and received a massive list of random crap. This is unreadable so I can only assume my workflow is wrong.
I think that models in OnShape can only be defined in a single document where all other documents permit read only. Users need to open the origin document to make changes. Is this true?
How do I visualize our documents, their contents, and which ones are pulling models from other documents?
Did my team really create documents for all these parts pictured?
If I search for type = part or assembly then open a result, will it always open the origin document (assuming "origin documents" exist)? Does it show a result for each "copy" in every document that references it?
Sorry to ask so many questions, but the guides are simply not useful. They just define what a Document, Assembly, and Part is, but not how to manage or garbage collect. My brain is used to Vault and other PDM tools that don't force things into containers and a reference is just a reference (like one big tree that can be viewed as everything above or below a node). Example: anything that uses Part A uses the one and only instance of Part A. Changes to Part A are automatically pulled in all parent assemblies. Another example: I can click on an Assembly B and "look up" to see everything that directly or indirectly references it or "look down" to see everything that Assembly B directly or indirectly references.