Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:

  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. 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.

tim_hess427 PRO

About

Username
tim_hess427
Joined
Visits
410
Last Active
Roles
Member
Points
76
Badges
5
Posts
85

Comments

  • @david_parker8532 - I see! So, its really the other folks using tools outside of onshape that's causing the issue. I wish I had other suggestions. Best of luck bringing them over to the light side and just using onshape to view! Maybe if/when …
  • @david_parker8532 - Is there a particular reason that the other users need to see the drawings in autocad?
  • I don't have a surface, but do have another 2-in1 device with stylus support. Several times, I've tried to move something around or zoom-in because I forget that gestures aren't supported. It would be great for presenting/review models where "…
  • @mlaflecheCAD - Thanks for the tips! I see that for branch management, I have two options - leaving the branches by creating versions on them and deleting the workspace (if appropriate) or I could just merge and delete the branch without creatin…
  • Thanks for the information @mlaflecheCAD! The last screenshot is interesting to me. To create that version tree, I'm assuming changes from B2 and B1 were merged back into Main for between each of the releases. Is that right? One thing I've thought a…
  • @mthiesmeyer - If we don't create a version on the branch, does the whole branch disappear when the workspace is deleted?  What happens to all of the micro-versions created on the branch? Are they lost too? @adrian_velazquez - Correct (for the mome…
  • 3dcad said: I think they should give 1 additional account for boss with any company account purchases. This way also the person who makes the decisions would have access to cad and that might lead to more accounts for employees in small compa…
  • Totally agree that having a place to see links and references would be great. After reading this, I was hopeful that a workaround could be adding the part number reference to the title block of a drawing, and then searching for that. However, it doe…
  • I don't think STL files actually store in/mm/m information. So its up to the software that's reading the file (your slicer) to convert the size to the correct unit. If I remember correctly, Cura uses mm by default (or may only use mm). So, I would c…
  • Glad to help!
  • It looks like your document is not public, so I am not able to open it and see what is going on. However, there are two things that you should check: * If you are extruding from a sketch to create a new feature that should be connected to the base…
  • That's interesting. When you're changing these features, are you deleting them and re-making them?  
  • I'm a little conflicted on this topic. How nice a model looks definitely has an impact on how a design is perceived, especially for people detached from the design process, such as managers, customers, sales team, etc. So, I think there is real valu…
  • @raj_Onshape - I imagine any part studios in the release branch to function like a read-only part studio where all of the parts are "derived" from the latest release for each part. Right now I can open a part studio and manually derive all of …
  • Oh! Yes - that sounds awesome.  That would also probably make it easier to share things with outside users (suppliers, manufacturing, etc.) without having to create "cleaned" documents to hide in-progress or unrelated data. 
  • @owen_sparks - How would you ensure that the "released" branch only has released parts/assemblies/drawings? If I merge my development branch into "released", wouldn't the current state of everything merge, released or not? I may be missing something…
  • I just wanted to drop in here because I referenced this thread in a discussion about release workflows: https://forum.onshape.com/discussion/11041/release-management-workflow-procedure#latest Your discussion here sparked an idea that I think is int…
  • @brucebartlett - Exactly. I was thinking about setting this scenario up and testing it myself, but one thing that would be required is to remove the ability and need to merge things into the main branch. Rather than merging changes to the main branc…
  • @NeilCooke - what about people signing up to be able to view files (partners, suppliers, etc.). Are we supposed to refer them to the "request a trial" sign up? If a document is shared directly to someone's email address, will they see language about…
  • I think this discussion is very closely related to the discussion over here: https://forum.onshape.com/discussion/10952/always-wip In that thread, @adrian_velazquez made a really good point about the default view of a document being the main worksp…
  • @jon_lewis118  - do you use any of the premium Asana features for this workflow, or do you have the free version? This looks pretty good!
  • Its less than two months later and I forgot about my previous comment here. I just found myself wondering "How do I start an extrude from an offset distance? Isn't that an option?"  Apparently not yet. 
  • @adrian_velazquez - That's an interesting idea. I supposed you could hack user permissions to revoke/grant user access to the documents, but that seems like it could be a hassle. At some point, it would be interesting to see change-requests build in…
  • Agreed - and we are looking at a variety of systems.  One thing that's come out of that research is different systems have different levels of capability for dealing with the engineering documentation. They all reference part numbers, but don't alw…
  • I've also taken to making a couple of different assemblies - one is kept up-to-date with the latest released version of each part. The other just has the WIP parts from the current workspace. This way I can see how part updates affect the assembly q…
  • Hi @owen_sparks, thanks for the perspective! We've actually got the prefixes now, but reading some books had me looking at the suffixes. I'm likely thinking too hard about this Do you enforce a rule that files related to the same part share t…
  • Building on what @michael_bromley said - since the comments have 'tasks' that can be assigned to people, it would be great if we could then reference one or more "changes" in the history list that were made in response to that task. 
  • @billy2 - One thing that I think is hidden in the assembly release workflow  - If your assembly is linked to released versions of your parts, they will not be bumped when you release the assembly.  I struggled with the same thing early on! So, if y…
  • @Cris_Bowers - thanks for the feedback. I was thinking more about using the suffix to tie different document types back to the part. So, for example: * 123456-00 (or maybe just "123456") = part * 123456-01 = Drawing * 123456-02 = STL file export *…
Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Badges

First Answer25 Up Votes10 Comments5 Up VotesFirst Comment