Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
Community
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Derive Parts not linking when moved

Derive Parts not linking when moved

I have a standards folder with large assemblies for library parts. In factory programs, all I want is a simplified part of that assembly to BOM and link to the base assembly. When create a derived part in the standards folder with the base assembly then move the derived part to the library, I cannot update the derived part if the base assembly updates to a new version. When I check the derived part out in the Library, I get a dongle warning me that someone else check that file out even though I am the one who just checked the file out. 

 

When moving files inside of Vault, Vault should track all links to any file and this error should not show; and the warning itself is incorrect. 

xxx.png

2 Comments
Anonymous
Not applicable

Hi, 

 

Fully agree. As workaround, you can iLogic to change the referenced file, in Inventor : 

 

 

Dim oDoc as Document
oDoc = ThisDoc.Document
Dim oRefFile As FileDescriptor
Dim oOrigRefName As Object     

For Each oRefFile In oDoc.file.ReferencedFileDescriptors
'get the full file path to the original internal references
oOrigRefName = oRefFile.FullFileName
 
'present a File Selection dialog
Dim oFileDlg As inventor.FileDialog = Nothing
InventorVb.Application.CreateFileDialog(oFileDlg)
oFileDlg.InitialDirectory = oOrigRefName
oFileDlg.CancelError = True
On Error Resume Next
oFileDlg.ShowOpen()
If Err.Number <> 0 Then
Return
ElseIf oFileDlg.FileName <> "" Then
selectedfile = oFileDlg.FileName
End If
 
'Replace the reference
oRefFile.ReplaceReference (selectedfile)     
InventorVb.DocumentUpdate()
oOrigRefName = ""                                        
Next
 
iLogicVb.UpdateWhenDone = True
---------------------
 
 
Hope this helps.
Anonymous
Not applicable

Hi Irenee,

 

Thanks for the (ILogic) script! I did find a workaround also. Not sure how others do this in the industry (but would love to know).

 

  1. In the Vault.ipj project working folders: Create a Standard part assembly (A) in the working folders called “Standards”. This will eventually become a library part but built for manufacturing with sheet metal workflows, vendor parts, etc. Final release REV 1.
  2. Create a part in the library using the Library.ipj project. Derive the assembly (A) from here as a simple surface part and save into the Library folder. When checking out, must select the vault.ipj project as reference. This part can be shared and linked, (read only), for use in “Factory Design Utilities” and other Autodesk products.
  3. Rev the base assembly (A) to REV 2 and now the Derive part will update BUT Vault will not let you know that the base assembly has updated and the derived part is now not the latest. Opening the derived part will show that the derived assembly was updated and not the latest.

 

PROBLEM: The assembly (A) I used before this example above, had an AutoCAD dwg X-REF attached to a part. Using the same procedure above, when creating derived part, checking that part in, Vault wanted to add the dwg as a new file. I don’t want two separate reference files!!!

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea  

Autodesk Design & Make Report