Parts showing in Vault Browser tree but not in Model browser tree

[Nauld1]

I noticed that there are 2 parts showing in my vault browser that I would like to remove from this assembly. But I can't seem to find these parts in the model browser in order to delete them. See picture below.

[blandb]

Are any of these parts derived from those 2 files? Maybe those are a master file of some sort?

[Nauld1]

That was my first thought, but no

[blandb]

Can you post your files?

[johnsonshiue]

Hi! Two possibilities.

1) The two parts are not derived to other parts but they are linked (parameters) to some parts.

2) Occurrence corruption due to prior usage. The two parts were used to create assembly features or frames on Inventor 2015 or earlier. The features and frames were deleted along with the sketch parts. But, the reference remains there.

Many thanks!

[Matthew_Policelli]

We had a user do #1 in one of our assemblies 8 years ago, and it went undetected until today. During those  8 years, it was copy designed 3 times, with those linked parts being copy designed as well despite no longer being in the assembly at some point. So basically we ended up with a bunch of unused, unnecessary parts in vault that are tied to the assembly but unused and not in the model tree.

Searching vault reveals user who linked the parts as parameters has also touched a lot of other assemblies. Many of those assemblies have probably also been Copy Designed in the past 8 years, so we could potentially have a lot of assemblies with this issue. Is there some way of finding files that have linked parts in the user parameters through Vault, or do we just have to keep an eye out for these and hope that this was an outlier?

[johnsonshiue]

Hi Matthew,

Likely this is an Inventor bug. It means Vault detects the document links but Inventor browser does not show such link. Go to Tools -> Link and see if such link is there. If not, it is a bug. Please share the files that exhibit the behavior, I would like to take a closer look. If you know how to reproduce the behavior from scratch, it will be very helpful to find a fix.

Many thanks!