What is Merge Scope in Onshape? (Explained with Examples)

Merge Scope in Onshape: A Guide for Beginners

Onshape is a cloud-based CAD platform that allows users to create, edit, and share designs with others in real time. One of the most important features of Onshape is its merge scope functionality, which allows users to control which changes are merged into a design when multiple users are working on it simultaneously.

In this guide, we will discuss what merge scope is, how it works, and how to use it effectively. We will also provide some tips for troubleshooting merge scope issues.

By the end of this guide, you will have a solid understanding of merge scope and how to use it to collaborate effectively with others on Onshape.

What is Merge Scope?

Merge scope is a feature in Onshape that allows users to control which changes are merged into a design when multiple users are working on it simultaneously. When a user makes a change to a design, that change is added to their local workspace. If another user makes a change to the same design, their change is also added to their local workspace.

When two users want to merge their changes into a shared workspace, they can use merge scope to specify which changes they want to merge. This allows users to avoid conflicts and ensure that the shared workspace contains only the changes that they want.

How does Merge Scope Work?

Merge scope works by creating a hierarchy of changes. The top level of the hierarchy is the shared workspace. Each user’s local workspace is a child of the shared workspace. When a user makes a change to a design, that change is added to their local workspace.

When two users want to merge their changes into the shared workspace, they can use merge scope to specify which changes they want to merge. The changes that are merged are added to the shared workspace as children of the user’s local workspace.

This hierarchy of changes allows users to see which changes were made by which users and when. It also allows users to roll back changes if necessary.

How to Use Merge Scope Effectively

Merge scope is a powerful tool that can help users collaborate effectively on Onshape. However, it is important to use merge scope correctly in order to avoid conflicts and ensure that the shared workspace contains only the changes that you want.

Here are some tips for using merge scope effectively:

• Use merge scope to specify which changes you want to merge. This will help you avoid conflicts and ensure that the shared workspace contains only the changes that you want.
• Be aware of the hierarchy of changes. The changes that are merged are added to the shared workspace as children of the user’s local workspace. This means that you can roll back changes by deleting the child changes.
• Use merge scope to roll back changes if necessary. If you accidentally merge a change that you don’t want, you can roll back the change by deleting the child change.

By following these tips, you can use merge scope effectively to collaborate effectively on Onshape.

“`html

        merge('Assembly1');
      

        merge('Component1');
      

        merge('Feature1');
      

“`

What is Merge Scope?

Merge Scope is a feature in Onshape that allows you to control which changes are merged into a document when you are collaborating with others. By setting the Merge Scope, you can specify which parts of the document are considered to be “local” and which parts are considered to be “global.”

Definition of Merge Scope

Local changes are changes that are made to a document that are specific to a particular user. For example, if you add a new feature to a part, that change is considered to be a local change. Global changes are changes that are made to a document that are shared by all users. For example, if you change the name of a part, that change is considered to be a global change.

Different types of Merge Scope

There are three different types of Merge Scope in Onshape:

• Local Merge Scope: This is the default Merge Scope. When Local Merge Scope is enabled, only local changes are merged into a document when you are collaborating with others.
• Global Merge Scope: When Global Merge Scope is enabled, all changes are merged into a document when you are collaborating with others.
• Inherit Merge Scope: When Inherit Merge Scope is enabled, the Merge Scope of a document is inherited from the parent document.

How to set Merge Scope

To set the Merge Scope of a document, you can use the following steps:

1. Open the document that you want to set the Merge Scope for.
2. Click the Manage tab.
3. Click the Merge Scope button.
4. Select the desired Merge Scope from the list.

When to Use Merge Scope?

The best way to decide when to use Merge Scope is to consider the following factors:

• The type of changes that are being made: If the changes are local, then you should use Local Merge Scope. If the changes are global, then you should use Global Merge Scope.
• The number of users who are collaborating on the document: If there are only a few users who are collaborating on the document, then you can use Local Merge Scope. If there are a lot of users who are collaborating on the document, then you should use Global Merge Scope.
• The importance of the document: If the document is important, then you should use Global Merge Scope to ensure that all users are working on the same version of the document.

When to use Local Merge Scope

You should use Local Merge Scope when you are making changes to a document that are specific to your own work. For example, if you are adding a new feature to a part, you should use Local Merge Scope so that your changes do not affect other users.

When to use Global Merge Scope

You should use Global Merge Scope when you are making changes to a document that are shared by all users. For example, if you are changing the name of a part, you should use Global Merge Scope so that all users are working on the same version of the document.

When to use Inherit Merge Scope

You should use Inherit Merge Scope when you are working on a document that is a child of another document. The Merge Scope of the child document will be inherited from the Merge Scope of the parent document.

Merge Scope is a powerful feature that can help you to collaborate with others on documents in Onshape. By understanding the different types of Merge Scope and when to use them, you can ensure that your documents are kept up-to-date and that everyone is working on the same version.

Here are some additional resources that you may find helpful:

• [Onshape Help Center: Merge Scope](https://help.onshape.com/articles/merge-scope)
• [Onshape Community: Merge Scope](https://community.onshape.com/c/collaborate/merge-scope)

Merge Scope is a feature in Onshape that allows you to control which parts of a document are merged when you check in changes. This can be useful for preventing conflicts when multiple users are working on the same document, and for ensuring that only the changes you want are merged into the master copy.

To use Merge Scope, you first need to create a scope. A scope is a set of parts or assemblies that you want to merge together. You can create a scope by selecting the parts or assemblies you want to include, and then clicking the “Create Scope” button.

Once you have created a scope, you can check in your changes. When you do this, Onshape will only merge the changes that are included in the scope. This prevents conflicts from occurring when multiple users are working on the same document.

Merge Scope can also be used to prevent changes from being merged into the master copy. To do this, you can create a scope that excludes the parts or assemblies that you do not want to merge.

Merge Scope is a powerful tool that can help you to collaborate more effectively with other users on Onshape. By using Merge Scope, you can prevent conflicts, ensure that only the changes you want are merged, and protect the master copy of your documents.

There are several benefits to using Merge Scope in Onshape, including:

• Improved collaboration: Merge Scope can help you to collaborate more effectively with other users by preventing conflicts and ensuring that only the changes you want are merged.
• Reduced conflicts: Merge Scope can help to reduce conflicts by preventing changes from being merged that would cause a conflict.
• Increased productivity: Merge Scope can help you to increase your productivity by allowing you to focus on the changes that you need to make, and by preventing conflicts from slowing you down.

There are a few common Merge Scope issues that you may encounter, including:

• Conflicts: If you encounter a conflict, you will need to resolve it before you can check in your changes. To resolve a conflict, you can either accept the changes from the other user, or you can reject the changes and make your own changes.
• Missing parts: If you are missing parts when you check in your changes, this may be because the parts are not included in your scope. To resolve this issue, you can either add the parts to your scope, or you can check in your changes without the parts.
• Unexpected changes: If you see unexpected changes when you check in your changes, this may be because the changes were not included in your scope. To resolve this issue, you can either add the changes to your scope, or you can reject the changes and make your own changes.

If you are having trouble troubleshooting a Merge Scope issue, you can contact Onshape support for help.

Merge Scope is a powerful tool that can help you to collaborate more effectively with other users on Onshape. By using Merge Scope, you can prevent conflicts, ensure that only the changes you want are merged, and protect the master copy of your documents.

What is Merge Scope in Onshape?

Merge scope is a feature in Onshape that allows you to control which parts of a document are merged when you merge two documents. This can be useful for keeping track of changes that have been made to different parts of a document, or for preventing changes from being overwritten when you merge two documents.

How do I set the merge scope in Onshape?

To set the merge scope in Onshape, follow these steps:

1. Open the two documents that you want to merge.
2. Click the Merge button.
3. In the Merge Scope dialog box, select the parts of the documents that you want to merge.
4. Click Merge.

What happens when I merge two documents with different merge scopes?

When you merge two documents with different merge scopes, the parts of the documents that are not in the common merge scope will be overwritten by the parts of the document that are in the common merge scope.

How can I use merge scope to keep track of changes that have been made to different parts of a document?

You can use merge scope to keep track of changes that have been made to different parts of a document by creating a separate document for each part of the document. Then, when you make changes to a part of the document, you can merge the changes into the corresponding document. This will allow you to keep track of all of the changes that have been made to each part of the document.

How can I use merge scope to prevent changes from being overwritten when I merge two documents?

You can use merge scope to prevent changes from being overwritten when you merge two documents by creating a separate document for each part of the document that you want to protect. Then, when you merge the two documents, you can specify that the parts of the documents that are in the separate document should not be merged. This will prevent any changes that have been made to those parts of the documents from being overwritten.

merge scope is a powerful tool in Onshape that can be used to manage and control the merging of changes between multiple documents. By understanding the different types of merge scopes and how they work, you can use merge scope to improve collaboration and productivity in your team.

Here are some key takeaways from this article:

• Merge scope allows you to control which changes are merged into a document.
• There are three types of merge scopes: local, shared, and global.
• Local merge scope applies to the current document only.
• Shared merge scope applies to all documents in a workspace.
• Global merge scope applies to all documents in the Onshape cloud.

By using merge scope effectively, you can ensure that your team is working on the same version of the design and that changes are merged in a controlled and consistent way.