Kuid Table

[dricketts]

What is the easiest way to delete kuid's from the kuid table for a route? This way they won't show as a missing dependency of the route.

 

[mrscsi]

What is the easiest way to delete kuid's from the kuid table for a route? This way they won't show as a missing dependency of the route.

The easiest would be to go in to CCP if you know the kuid and just delete it from there. You could also do it editing the config in Notepad as well.

 

[sniper297]

Contrary to popular belief, I am not a mad hacker - I hack when it's safe, more efficient, or the only option. If the officially approved method works easily and reliably enough I always use that.

So, step 1: Find the KUID I want to get rid of in Content Manager, Save it to CDP, then delete it.
2: Open the route in surveyor, click Main menu, Delete Missing Assets, save route.
3: Back to Content Manager, select the route and Check Dependencies, View in Main List. Make sure that KUID is gone, then reinstall it from the CDP if I need it for something else.

Directly hacking the config.txt to remove the KUID means the undesirable asset will no longer be listed as a dependency, but the code for it will still be in one of the files, which could cause other problems.

 

[Dermmy]

Directly hacking the config.txt to remove the KUID means the undesirable asset will no longer be listed as a dependency, but the code for it will still be in one of the files, which could cause other problems.

Sorry Snipe, but 'directly hacking' (which i assume is a deliberately chosen, emotive, overly dramatic phrase for which most of us would substitute the much more socially acceptable term 'Editing') the kuid from the kuid table will have absolutely no effect whatsoever on the route, the asset or the asset's appearance on the route.

You are absolutely right that 'editing' the config's kuid table will not remove the asset from the route, but the undefined 'other problems' to which you allude are non existent. The kuid will simply get written back to the kuid table on the next save...

Andy