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

KB42879: ScanMD custom test 310003 is unable to remove a duplicate column although the opposite is reflected in the ScanMD log.


Community Admin

• Strategy


This technical note describes a specific scenario where ScanMD custom test is not able to remove a detected duplicate column.

SYMPTOM:
ScanMD custom test 310003 detects a duplicate column and according to the logs it can successfully remove it, as shown in the trace below:


: Column COL has an unnecessary column duplicate named COL(1) with ID (xxxx)
: Column COL has an unnecessary column duplicate named COL(1) with ID (xxxx)
: Column COL has an unnecessary column duplicate named COL(1) with ID (xxxx)

However, when accessing the project, the column remains and if ScanMD is run again, the same column is detected.
When looking for dependents of that column, a shortcut shows up. Column dependencies can be found by following the steps below:

  1. Unhide the System Objects folder, as per technical note KB19828: How to display hidden and invisible folders/objects in MicroStrategy Desktop 9.x.
  2. Navigate to System Objects\Columns folder.
  3. Right click on the duplicate column name and select "Search for Dependents..."

 
CAUSE:
This issue occurs because there is a shortcut to the column that ScanMD custom test 310003 is trying to remove.
 
ACTION:
Remove the shortcut manually and run ScanMD custom test 310003 again. 
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 6, 2017

Last Updated:

April 6, 2017