topic Re: Assembly structure not visible in Vault Client 2023 after rename in Vault Customization Forum

Assembly structure not visible in Vault Client 2023 after rename

bshinde3ZRN3 — Thu, 04 Sep 2025 10:28:13 GMT

Hello Sir,

I’m currently working on a customization project involving Autodesk Inventor and Vault. As part of the workflow, I checked in an assembly named assembly1.iam into Vault. This assembly includes two child components: part1.ipt and part2.ipt. After the initial check-in, the Vault Client correctly displayed both child parts under the Uses tab.

Following this, I executed a custom action via a button that programmatically performs the following steps:

Checks out the assembly.
Renames the child parts first, followed by the assembly.
Updates the references accordingly.
Checks the renamed assembly back into Vault.

After this process, the renamed assembly opens correctly in Inventor along with its renamed child components, indicating that the references are intact. However, in the Vault Client, the Uses tab no longer displays the child associations for the renamed assembly.

Could you please advise why these associations are not visible in Vault Client and how this issue can be resolved?

Thank you,

Re: Assembly structure not visible in Vault Client 2023 after rename

Richard.Rankin — Thu, 04 Sep 2025 10:38:51 GMT

Hi @bshinde3ZRN3

Can you reproduce this behaviour when you manually follow those steps? (Using the User Interface).

If you cannot reproduce the issue manually, it may be a problem with your code that would be best addressed by posting this question in the Vault Customisation forum.

Re: Assembly structure not visible in Vault Client 2023 after rename

bshinde3ZRN3 — Thu, 04 Sep 2025 10:46:19 GMT

Hi Richard,

I performed same steps using UI and i am able to see the structure in Vault Client without any issues. I am expecting similar behavior when I am doing it programmatically. But it is not working. Similar behavior is happening with a simple part and its associated drawing.

Thanks,

Bhushan

Re: Assembly structure not visible in Vault Client 2023 after rename

ihayesjr — Thu, 04 Sep 2025 16:33:29 GMT

@bshinde3ZRN3

Why are you building something custom to rename the children?

Where are the new names coming from?

Re: Assembly structure not visible in Vault Client 2023 after rename

bshinde3ZRN3 — Fri, 05 Sep 2025 06:38:44 GMT

We are currently working on integrating Vault with 3DX. As part of this process, it's important to note that 3DX enforces strict naming conventions within Enovia—parts must adhere to specific naming rules provided by 3DX. The customer has requested that all legacy data be renamed to align with these conventions. To support this, we are renaming the assemblies using the new names supplied by 3DX.

I am using below function RenameFileViaUpload to rename the parts first, then i am using another function RebuildAssemblyFromVaultStructure to update the references in assembly, then i am calling RenameFileViaUpload to rename assembly. Here are the functions:

public static void RenameFileViaUpload(
VDF.Vault.Currency.Connections.Connection connection,
Autodesk.Connectivity.WebServices.File file,
string newName)
{
try
{
var wsFolder = connection.WebServiceManager.DocumentService.GetFolderById(file.FolderId);
var vdfFolder = new VDF.Vault.Currency.Entities.Folder(connection, wsFolder);

// Step 2: Get the local working folder path
string localFolderPath = connection.WorkingFoldersManager.GetWorkingFolder(wsFolder.FullName).FullPath;

string originalFilePath = Path.Combine(localFolderPath, file.Name);
string newFilePath = Path.Combine(localFolderPath, newName);

//Checkout the file
MxLogger.LogEnovia("Checkout the file.");
VDF.Vault.Settings.AcquireFilesSettings aqSettings = new VDF.Vault.Settings.AcquireFilesSettings(connection)
{
DefaultAcquisitionOption = VDF.Vault.Settings.AcquireFilesSettings.AcquisitionOption.Checkout
};
FileIteration vdfFile = new FileIteration(connection, file);
aqSettings.AddEntityToAcquire(vdfFile);
AcquireFilesResults results = connection.FileManager.AcquireFiles(aqSettings);
FileAcquisitionResult fileAcquisitionResult = results.FileResults.FirstOrDefault();

// Step 3: Download the file to the local folder
MxLogger.LogEnovia("Download the file to the local folder.");
var acquireSettings = new VDF.Vault.Settings.AcquireFilesSettings(connection)
{
LocalPath = new VDF.Currency.FolderPathAbsolute(localFolderPath)
};
acquireSettings.AddEntityToAcquire(new VDF.Vault.Currency.Entities.FileIteration(connection, file));
connection.FileManager.AcquireFiles(acquireSettings);

// Step 4: Rename the file locally
MxLogger.LogEnovia("Rename the file locally.");
if (System.IO.File.Exists(newFilePath))
{
System.IO.File.Delete(newFilePath); // Avoid conflict
}
System.IO.File.Move(originalFilePath, newFilePath);

// Step 6: Upload the renamed file using FileManager.AddFile
MxLogger.LogEnovia("Upload the renamed file.");

using (var stream = new FileStream(newFilePath, FileMode.Open, FileAccess.Read))
{
var renamedFile = connection.FileManager.CheckinFile(
new FileIteration(connection, file),
"renaming to new name",
false,
DateTime.Now,
null,
null,
false,
newName,
Autodesk.Connectivity.WebServices.FileClassification.DesignDocument,
false,
stream
);
}
}
catch (Exception ex)
{
MessageBox.Show($"❌ Rename via upload failed for '{file.Name}': {ex.Message}", "Rename Error");
}
}

===============================================================

public static bool RebuildAssemblyFromVaultStructure(
Connection connection,
VaultFile renamedParentFile,
Dictionary<string, string> renameMap,
out string message)
{
message = string.Empty;
if (connection == null) { message = "❌ Null Vault connection."; return false; }
if (renamedParentFile == null) { message = "❌ Null parent file."; return false; }
if (renameMap == null || renameMap.Count == 0) { message = "❌ Empty rename map."; return false; }

Application invApp = null;
bool createdNewInstance = false;

try
{
// ---- Resolve latest WS File for the parent (the rename changed Name but ID stayed) ----
var ws = connection.WebServiceManager;
var parentLatest = ws.DocumentService.GetFileById(renamedParentFile.Id);
if (parentLatest == null)
{
message = $"❌ Could not resolve parent by Id: {renamedParentFile.Id}";
return false;
}

// ---- Acquire locally: CHECKOUT parent (we will Save), DOWNLOAD children ----
// Parent checkout
var parentIter = new FileIteration(connection, parentLatest);
var acqParent = new AcquireFilesSettings(connection)
{
DefaultAcquisitionOption = AcquireFilesSettings.AcquisitionOption.Checkout
};
acqParent.AddFileToAcquire(parentIter, AcquireFilesSettings.AcquisitionOption.Checkout);
connection.FileManager.AcquireFiles(acqParent);

// Gather children (latest) to compute their local paths and ensure they’re present
var childLatest = GetLatestChildFiles(connection, parentLatest);

if (childLatest.Count > 0)
{
var acqChildren = new AcquireFilesSettings(connection)
{
DefaultAcquisitionOption = AcquireFilesSettings.AcquisitionOption.Checkout
};
foreach (var f in childLatest.Values)
acqChildren.AddFileToAcquire(new FileIteration(connection, f),
AcquireFilesSettings.AcquisitionOption.Checkout);

connection.FileManager.AcquireFiles(acqChildren);
}

// Resolve parent local path using StatusResolution
var parentLocalPath = connection.WorkingFoldersManager.GetPathOfFileInWorkingFolder(parentIter).ToString();

if (string.IsNullOrWhiteSpace(parentLocalPath) || !System.IO.File.Exists(parentLocalPath))
{
message = $"❌ Local assembly path not found after acquire: {parentLocalPath}";
return false;
}

// Build NEW name -> local path lookup for renamed children
var newNameToLocalPath = BuildNewLocalPathLookup(connection, childLatest);

// ---- Attach or start Inventor headless ----
invApp = AttachOrStartInventor(out createdNewInstance);
invApp.SilentOperation = true;

// ---- Open assembly and replace references via descriptors ----
var asmDoc = (AssemblyDocument)invApp.Documents.Open(parentLocalPath, false);

int replaced = 0;
foreach (DocumentDescriptor dd in asmDoc.ReferencedDocumentDescriptors)
{
var oldLeaf = System.IO.Path.GetFileName(dd.FullDocumentName);
if (oldLeaf == null) continue;

if (renameMap.TryGetValue(oldLeaf, out var newLeaf))
{
if (newNameToLocalPath.TryGetValue(newLeaf, out var newFull) && System.IO.File.Exists(newFull))
{
dd.ReferencedFileDescriptor.ReplaceReference(newFull);// ✅ preserves constraints/placement
replaced++;
}
}
}

// Update & Save
asmDoc.Update();
if (!System.IO.File.GetAttributes(parentLocalPath).HasFlag(FileAttributes.ReadOnly))
{
asmDoc.Save();
}
else
{
message += "\n❌ File is read-only. Cannot save.";
return false;
}

asmDoc.Close(true);

// ---- Check-in parent WITHOUT explicit associations (let server extract refs) ----
connection.FileManager.CheckinFile(
parentIter,
"Updated assembly after rename",
false, // keepCheckedOut
DateTime.Now,
null, // file associations
null, // file link settings
false, // allow library update
null, // file classification
Autodesk.Connectivity.WebServices.FileClassification.DesignDocument,
false, // is content source
null // content source info
);

message = $"✅ Assembly updated and checked in.\nReplaced references: {replaced}\n{parentLocalPath}";

return true;
}
catch (Exception ex)
{
message = $"❌ Error rebuilding assembly: {ex.Message}";
return false;
}
finally
{
if (createdNewInstance && invApp != null)
{
try { invApp.Quit(); } catch { /* ignore */ }
Marshal.ReleaseComObject(invApp);
invApp = null;
GC.Collect(); GC.WaitForPendingFinalizers();
}
}
}

Re: Assembly structure not visible in Vault Client 2023 after rename

Markus.Koechl — Fri, 12 Sep 2025 08:17:33 GMT

You must capture the file associations before check out and provide these during check in. Your code comment (// ---- Check-in parent WITHOUT explicit associations (let server extract refs) ----) states what you are missing; the server does not extract the reference structure, the respective CAD plugin does it. So either call the Inventor user command to check in, or handle the associations. Find a code sample on how to to this here: Vault-Job-Processor---iLogic-Extension/Autodesk.VltInvSrv.iLogicSampleJob/iLogicJobExtension.cs at 2024.1 · koechlm/Vault-Job-Processor---iLogic-Extension

I hope this helps.

Re: Assembly structure not visible in Vault Client 2023 after rename

bshinde3ZRN3 — Mon, 22 Sep 2025 11:31:14 GMT

Hi Markus,

Thanks for your response. I reviewed the link you shared and wanted to share my findings based on three different approaches I tried:

First Approach
I fetched the associations from assembly1.iam just before check-out. Then, I renamed part1.ipt, part2.ipt, and assembly1.iam to part3.ipt, part4.ipt, and assembly2.iam respectively. After updating the references in assembly2.iam, I attempted to check it in using the original associations. However, this resulted in an exception because the associations were still pointing to the old file names (part1.ipt and part2.ipt), which no longer existed locally.
Second Approach
I checked out assembly1.iam, renamed the assembly and parts, and updated the references. Then I tried to fetch the associations, but none were found. It seems that renaming the files causes the associations to be lost.
Third Approach
I fetched the associations before check-out, renamed the files as in the first approach, and updated the references. During check-in, I created new associations using the data fetched earlier. This allowed me to see the associations in Vault. However, performing a "Get" operation on the files triggered an error dialog stating: "Unable to update file references."

From what I’ve observed, renaming both the parts and the assembly causes the original associations to be deleted. If I try to fetch associations from the renamed assembly just before check-in, none are generated, resulting in a zero count.

I’m unsure how to resolve this. Could you please advise where I might be going wrong?

Thanks,
Bhushan