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

KB39560: Attributes are seen as being dependent on logical tables even though no form is seen mapped to those tables from MicroStrategy Developer 9.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This technical note describes a behavior observed with attributes that seem to be dependent on logical tables when no forms are being mapped to such tables.

SYMPTOM:
Consider that a logical table needs to be deleted from a Strategy project. When checking for dependencies on the table from Strategy Developer, one or more attribute(s) show up. However, on editing the attribute(s) using Strategy Developer, no forms can be seen mapped to the logical table.
 
CAUSE:
One possible cause of this behavior can be that the attribute form mapped to the logical table has become hidden. As a result, Strategy Developer does not show the attribute form even if browsing for hidden objects has been enabled from Tools > Desktop Preferences > Browsing. The cause is similar to that described for the ID form in the following Strategy Knowledge Base technical note, but it can happen for any form category besides ID:
 
KB10715 (KB5700-7XX-1269): When editing attributes, no attribute forms are displayed even though the attribute works in a report on MicroStrategy Desktop 9.2.x - 9.3.x
 
In order to track down the cause of this inconsistency, customers encountering this issue should make note of Schema/Application-related changes, Object Migrations or error messages prior to experiencing the problem. Change Journaling, if enabled, can help in preserving this information.
 
ACTION:
 
Contact Strategy Technical Support for steps to resolve this issue.
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 20, 2017

Last Updated:

June 20, 2017