EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB45881: "Cannot delete 'xxx' because other objects depend on it. Do you want to search the dependent objects?" appears when deleting source tables from MicroStrategy Architect 9.x.


Community Admin

• Strategy


SYMPTOM:
Users are able to delete some logical tables that are used by objects but not all tables. Some tables get the message below preventing them from being deleted while others get the warning but upon selecting yes are removed. The first image below shows the warning message box that will be displayed at any time a table is deleted. The next image is the error that shows for certain tables that the product does not allow to be removed after selecting yes in the warning.
 warning:
 

ka04W000000OdU9QAK_0EM440000002CUe.png

 
 error:
 

ka04W000000OdU9QAK_0EM440000002CUc.png

 


Cannot delete 'LU_Gender' because other objects depend on it. Do you want to search the dependent objects?

CAUSE:
This works in this manner to allow for quicker deletion of secondary tables. If a table is not the primary lookup table (bold) of an attribute or directly used by another type of object (relationship filter, transformation). Then the objects that do use it can easily just have it unchecked as a source table. This is something the product can do automatically without requiring the end users to remove the table as a source table individually from every attribute and fact that uses it. This is done simply to allow for quicker architecting of an environment and is why the warning message is displayed.
The reason this can't be done for attributes that use the table as a lookup table is that each attribute must have one single lookup table (bold). If a lookup table was removed the Strategy product would have no means to know which of the other available source tables to pick as the new lookup table. Hence the error seen when those sorts of attributes are involved.
Below is an attribute showing which table is the primary lookup table. If this was the only attribute in the project then the LU_Customer table could be deleted while the LU_Gender table would not be. This is indicated by the LU_Gender table being bold.
 

ka04W000000OdU9QAK_0EM440000002CUZ.jpeg

 
ACTION:
If it is desired to prevent users from being able to delete any logical tables period, the easiest option is to use ACL's to make sure users/groups do not have the delete access to those objects. This can be done at the tables folder so it will apply to all newly created logical tables as well.
 


Comment

0 comments

Details

Knowledge Article

Published:

April 12, 2017

Last Updated:

April 12, 2017