Linked Document

breno_crucioli

In my current document, I have a subassembly where linked documents are located. This subassembly is located in my Main Assembly. When I create a new version of the "linked document" and update it in my subassembly, it works perfectly, but when I open my Main Assembly the changes are not there. Why does it happen?

billy2

@breno_crucioli I've been following this thread hoping for a solution for you.

I use the document in document design pattern a lot, all day long and I've been trying to get it to behave as you describe, but I can't. For me, it has always worked.

I'm also under NDA so I can't show you much, but here's my structure. Below is my project top level that has a pneumatic cylinder. It's 4 levels deep and I'll show you the structure:




Lowest level. Here's the imported McMaster Carr import of the cylinder. Notice I import all my McMaster stuff into a McMaster folder:




Level 2. I want that cylinder to work so I put it in it's own assembly (in the same document):


I also include the other stuff associated with a pneumatic cylinder like flow control and a coupler.



Level 3. I take this cyl assy and add it to press assy (same document):




Top level. Now I take the press and move it into the top assy (different doc):


They look the same but they're not. Wish I could show the whole assembly. If I could show the whole assembly, you'd see how it's scaling up in complexity.



So here's my structure:
top assy (xy doc) <-- press assy(press doc) <-- cyl assy (press doc) <-- cyl part studio(press doc)




Ok, so let's make a change in the cyl part studio. 1st, I have to activate the workspace (sq base). If you "open document" from the top assy, you'll be in a version. Can't work in a version, it's immutable (can't mutate):




Ok, here's the cyl assy and make sure you're in the activate workspace (sq base):




Now to the press assy level, and once again, make sure you're in the active workspace (sq base):




The next leap is to jump across documents to the top assy. I have to version the press assy so it'll show up in top assy:




Make sure your versions are named with good reasons.

Now I'm at the top assy and notice the blue update icon:




I update the top assy and...:


I use this design pattern all day long for many projects and it never fails. My only thought why it might not be working for you is possibly you're changing workspaces somewhere along the way. That's happened to me and it's why I'm real careful to keep my workspaces tidy.

It does work.

Possibly you should build a simple assy that's not confidential and let tech support help you.

andy_morris

Hi Breno,
Did you create a new version of the sub-assembly?
Regards,
Andy

breno_crucioli

Hi Andy. No, I didn't. My subassembly is not a linked document, it is an assembly inside my Main Assembly.

lana

@breno_crucioli
We should be able to help if you publish a link to your document.

john_mcclary

I cannot re-create this behavior unless i set the subassembly to a version as well.
Are you sure your sub assembly isn't set to a version of the main document?
Try setting a new version in the main document (that holds the assemblies) and see if you get the blue link on your subassembly

breno_crucioli

lana said:

@breno_crucioli
We should be able to help if you publish a link to your document.

Hi lana, it is not possible because my project is Confidential. Thank you for your help.

john_mcclary said:

I cannot re-create this behavior unless i set the subassembly to a version as well.
Are you sure your sub assembly isn't set to a version of the main document?
Try setting a new version in the main document (that holds the assemblies) and see if you get the blue link on your subassembly

Hi john_mcclary. I tried to create a new version of my document as you said, but my status doesn't change. The think is, when I create a new version of my "linked document" the blue link is available in the "linked parts" inside my "subassembly". But when I click in the Main Assembly (inside the same document) the changes of my "subassembly" are not there.

john_mcclary

If your document is confidential you will need to submit your question using the feedback tool in your document

breno_crucioli

There is no "Feedback" tool, there is "Report a bug".

john_mcclary

Could be because you are EDU, I'm sure it's the same thing

breno_crucioli

It's ok. Thanks for your help, I'll try it that way. I was not sure if my question was a bug or just did not know how to use Onshape.

billy2

@breno_crucioli I've been following this thread hoping for a solution for you.

I use the document in document design pattern a lot, all day long and I've been trying to get it to behave as you describe, but I can't. For me, it has always worked.

I'm also under NDA so I can't show you much, but here's my structure. Below is my project top level that has a pneumatic cylinder. It's 4 levels deep and I'll show you the structure:




Lowest level. Here's the imported McMaster Carr import of the cylinder. Notice I import all my McMaster stuff into a McMaster folder:




Level 2. I want that cylinder to work so I put it in it's own assembly (in the same document):


I also include the other stuff associated with a pneumatic cylinder like flow control and a coupler.



Level 3. I take this cyl assy and add it to press assy (same document):




Top level. Now I take the press and move it into the top assy (different doc):


They look the same but they're not. Wish I could show the whole assembly. If I could show the whole assembly, you'd see how it's scaling up in complexity.



So here's my structure:
top assy (xy doc) <-- press assy(press doc) <-- cyl assy (press doc) <-- cyl part studio(press doc)




Ok, so let's make a change in the cyl part studio. 1st, I have to activate the workspace (sq base). If you "open document" from the top assy, you'll be in a version. Can't work in a version, it's immutable (can't mutate):




Ok, here's the cyl assy and make sure you're in the activate workspace (sq base):




Now to the press assy level, and once again, make sure you're in the active workspace (sq base):




The next leap is to jump across documents to the top assy. I have to version the press assy so it'll show up in top assy:




Make sure your versions are named with good reasons.

Now I'm at the top assy and notice the blue update icon:




I update the top assy and...:


I use this design pattern all day long for many projects and it never fails. My only thought why it might not be working for you is possibly you're changing workspaces somewhere along the way. That's happened to me and it's why I'm real careful to keep my workspaces tidy.

It does work.

Possibly you should build a simple assy that's not confidential and let tech support help you.