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

KB19589: Error: "One or more columns were not found in table XXX." error message appears when adding or removing a table from the Warehouse Catalog Editor in MicroStrategy Developer 9.4.1. and 10.x.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


When adding or removing a table from the warehouse catalog in MicroStrategy Developer 9.4.1 and 10.x, users receive the following error message: "One or more columns were not found in table XXX. Other objects use some of these columns. Removing these columns can leave the affected objects in an inconsistent state. The table structure will not be updated until no objects depend on these columns. Please modify the definition of the affected objects before continuing. Click on 'Details' to see the list of affected objects."

SYMPTOM:
When adding or removing a table from the warehouse catalog in Strategy Developer 9.4.1 and 10.x, users receive the following error message:
 

ka02R000000kZKdQAM_0EM440000002Elk.jpeg

 


One or more columns were not found in table XXX. Other objects use some of these columns. Removing these columns can leave the affected objects in an inconsistent state. The table structure will not be updated until no objects depend on these columns. Please modify the definition of the affected objects before continuing. Click on 'Details' to see the list of affected objects.

 

This message occurs despite users having removed all dependents on the listed table.
 
CAUSE:
In this case, the table had been mirrored onto a table alias - where the dependents listed in the 'details' section of the error message were found.
 
ACTION:
Users experiencing this issue should be wary of table alias' and should carefully examine the list of affected objects to find a common parent object where the dependencies lie.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 16, 2017

Last Updated:

June 16, 2017