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.

Is it possible to have multiple users viewing different display states of an assembly at once?

We have run into an issue where we have multiple users working in an assembly and when switching display states it seems to switch display states for all users which is very frustrating. Is there another tool we should be using to create or manage display states for user to work in different areas of the design at once?

Best Answer

  • S1monS1mon Member Posts: 2,246 PRO
    Answer ✓
    Isolate and Make Transparent are temporary viewing states per window/user. You probably want to focus on using these commands. You can't save selections for these commands, but you might be able to organize your instance list in a way that makes it easier to recreate the appropriate selections (folders can be useful, or filtering by names).

    Hide/Show is per workspace and affects all windows/users. These are really less useful because of how they affect everyone. I'm ok using them temporarily on documents that are unlikely to be opened by multiple users at once.

    Display states are built on top of Hide/Show and it sounds like they affect all users.

    I like to set up assemblies so that "show all instances" will leave the assembly in the correct state for whatever the released revision is. 

    You may also want to look at configurations to suppress parts for those situations where one user is only working on a subset of the parts.

Answers

  • S1monS1mon Member Posts: 2,246 PRO
    Answer ✓
    Isolate and Make Transparent are temporary viewing states per window/user. You probably want to focus on using these commands. You can't save selections for these commands, but you might be able to organize your instance list in a way that makes it easier to recreate the appropriate selections (folders can be useful, or filtering by names).

    Hide/Show is per workspace and affects all windows/users. These are really less useful because of how they affect everyone. I'm ok using them temporarily on documents that are unlikely to be opened by multiple users at once.

    Display states are built on top of Hide/Show and it sounds like they affect all users.

    I like to set up assemblies so that "show all instances" will leave the assembly in the correct state for whatever the released revision is. 

    You may also want to look at configurations to suppress parts for those situations where one user is only working on a subset of the parts.
  • tim_hesstim_hess Member Posts: 46 ✭✭
    Honestly - if multiple people are actually "working" and editing the model at the same time, this seems like a good use case for branching in merging. Each user can create a branch and work in their own workspace un-affected by people working in other workspaces. 

    I also wish there was a way to force "view-only" mode for the times you just want to inspect something but don't want to affect ongoing work or accidently change something. Even show/hide create actions in the document history which could obscure actual model edits. 
  • eric_pestyeric_pesty Member Posts: 1,395 PRO
    Another related "tip" that may or may not be applicable is that if you just want to look at an assembly in "view only" mode, you can pick the last version (or microversion) before the workspace and then you can show hide things without making any actual changes that would affect other users... This also works if you want to rollback the tree in a part studio to understand how a part is made for example.
Sign In or Register to comment.