The attached video shows exactly why, at times, but on a quite frequent basis these days, I feel a somewhat overwhelming urge to take a sledge hammer to my Vault server and go back to using a filing cabinet.
I know Vault inside out and back to front, short of understanding it at SQL table level, and when I see stuff like this I just hang my head in defeat.
Be under no illusions, make no presumptions, the Item in the video is brand new and as simple as it gets. It has 17 versions because I'd edited/updated it that often trying to troubleshoot it before I made the video. The Item has never been released, it was originally linked to a basic A4 AutoCAD DWG with no xrefs or links to any other entity. This, is a basic simple standalone Item.
I will personally hand over £20 to anyone who can explain why the hell it says the Item has a link to a parent. I will not take 'Vault is crap' or 'its obviosuly a bug' as a valid answer.
On a side note. Selecting 'Update' on the item will list 6-7 other Items as if the Item has a BOM. Renumbering this Item to anything else works, but then Vault still thinks the original Item number is still in use. It's... I give up.
Have you tried checking the box that says ignore restrictions?
Aye, I know how to delete an item. I was asking if anyone can explain why an Item would think it has an active link to a parent when there is clearly no link or 'where used' data at all.
Did it have a parent link at any time in it's life?
Neil
You know me, anything for £20.....
As you know, we dont use Items, but weve had similar problems with assemblies...
You tried purging the items? (if you can) thats how we fixed the iam files
If you cant purge Items then i guess no £20........
Cheers
Graeme
Most likely the issue is that an older version of that parent Item is referencing the Item that can not be deleted.
Please note that ,even if you were to delete the parent item you may still see this message when deleting the child for as long as 24 hours.
Doing all operations in real time can be too costly (in perfromance) so we often have background processes that clean up data later.