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

KB13127: How to obtain Project Documentation on dependent or component objects In MicroStrategy Developer


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Sometimes it is necessary to view the details of objects that are dependents or components of another object. This can be easily accomplished using Project Documentation in Strategy Developer. The issue here is how to limit the Project Documentation to the dependents or components of an object.
To view the details of components of an object, follow the steps below:
 

  • Navigate to the desired object in Strategy Developer, right-click and select 'Search for Components', as shown below:
ka0PW00000019VuYAI_0EM440000002Fab.jpeg
  • NOTE: Search for Dependents will also allow the same project documentation steps if those are the objects needed to be viewed.
     
  • After the search has completed, highlight all objects, right-click, and select 'Project Documentation', as shown below:
ka0PW00000019VuYAI_0EM440000002FaX.jpeg
  • Select any preferences in Project Documentation to view the details of the dependents. The project documentation appears similarly to the image below:
ka0PW00000019VuYAI_0EM440000002Fac.jpeg
  • The Project Documentation should look like the generic Project Documentation. To modify the page title and the subtitle section entitled 'Project Documentation' for storage purposes, there are two sections (highlighted in bold) to modify in the first few lines of all of the HTML files:
    <HTML>
    <HEAD>
    <TITLE>Duplicated Strategy Tutorial</TITLE>
    <LINK REL=stylesheet HREF="Auxiliary Files\style.css" TYPE="text/css">
    </HEAD>
    <BODY TOPMARGIN=1 LEFTMARGIN=1 MARGINRIGHT=1 MARGINBOTTOM=1 LINK=#000000 VLINK=#000000 ALINK=#000000>
    <TABLE CLASS=MAINBODY WIDTH=598 CELLSPACING=0 CELLPADDING=1>
      <!-- ############## -->
      <!-- # # -->
      <!-- ############## -->
      <TR HEIGHT=80 VALIGN=TOP>
       <TD>
        <TABLE CLASS=MAINBODY WIDTH=100% CELLSPACING=0 CELLPADDING=1>
         <TR>
          <TD CLASS=MAINBODY WIDTH=55 ROWSPAN=2><IMG src="C:\Program Files\MicroStrategy\Desktop\Images\ProjectDoc\Main.jpg"></TD>
          <TD CLASS=PROJECTNAME>Duplicated Strategy Tutorial</TD>
         </TR>
        <TR><TD CLASS=SUBTITLE>Project Documentation</TD></TR>
       </TABLE>
      </TD>
    </TR>
  • If these two sections are changed to say 'Documentation for Components of 'Report'', the resulting documentation page is more explanatory:
ka0PW00000019VuYAI_0EM440000002FaN.jpeg

NOTE: This process is done manually on every HTML page in the documentation.
 


Comment

0 comments

Details

Knowledge Article

Published:

April 13, 2017

Last Updated:

March 7, 2024