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.
- Last Active
@philip_thomas That makes sense. Our team has been moving any part studio which is referenced by more than one document to it's own document, along with all relevant drawings. It really does make it … (View Post)3
@pete_yodis - The version mechanism is, in my opinion, the killer app in OnShape. As @michael_bromley and @brucebartlett have noted, versioning is not an effective navigation or browsing tool. It is,… (View Post)2
I have a bit of a software background and find the Onshape versioning philosophy quite intuitive - it is the same process used for software release management. The whole point is to have each 'versio… (View Post)3
In our company, the version approach is also useful as a communication tool between Engineering and Manufacturing: Each time a part is updated, we create a new version named "Production" + … (View Post)5
(Quote) I agree, in the majority of cases the feature requests should take priority. However there is definitely a need in any development/design organization for skunkworks style developmen… (View Post)1