Delete Failed. The item could not be deleted.

Delete Failed. The item could not be deleted.

Last Updated: May 09, 2013 02:34PM CDT

Problem

When trying to delete a Location in Asset Manager, you get the following error or one similar to it:
 

The item could not be deleted: Cannot delete type " ". There are one or more objects scoped to the type.

Object type: Polyline Hot Spot
Asset name: null

Discussion

The error message indicates that there is still an upstream link to the Location you are trying to delete.

For the example above, a Hot Spot was pointing from a higher level (Austin) down to the Location (RF Code HQ) that was trying to be deleted:

Another similar error you might encounter is the following:
 

The item could not be deleted: Cannot delete type " ". There are one or more objects scoped to the type.

Object type: Map
Asset name: Location = Austin (Geographical)

Before an item or location can be deleted, all references to that item or location must be deleted. The following are certain types of items in discussion, where they're found, and any specific considerations where appropriate:
 

• Assets (User Console -> Assets -> Manage Assets by Location)
       Either move or delete the assets.
   
• Reports & Graphs (User Console -> Reports/Graphs) 
   
• Dashboards (User Console -> Dashboard)
   
• Location to Asset Association (Admin Console –> Locations/RulesMaps -> Locations to Asset Association)
   
• Maps (Admin Console -> Locations/Rules/Maps -> Map Configuration)
       Also check for references from higher level maps.
   
• -Rules (Admin Console -> Locations/Rules/Maps) 

Solution

In the Location hierarchy, look "up" one level at a time until you find the Location or Map or other item that points to the one you are trying to delete. Then, remove the association (reference).  Additionally, you may be able to find more difficult dependencies by exporting the entire Asset Manager configuration and Data Schema using "Admin Console -> Configuration -> Export Configuration" as "CSV", then search the CSV(s) file for the dependency named in the error, then navigate in the Asset Manager interface to that asset/entity and delete it from the Asset Manager interface.