KB46742: How to Set the Page-By Field to Open by Default using the MicroStrategy Web SDK 9.4.1

In Strategy Web, the page-by field does not appear by default if there is no page-by present.  The following steps will show how to set the page-by to open by default regardless if the report has a page-by field or not:
 

 
Using the Strategy Web Customization Editor:

1. Launch the Web Customization Editor.
2. Create a new plug-in and give it a meaningful name.
3. Click in Strategy Web Configuration inside the Application Settings view to expand the hierarchical tree. The expanded list comprises the different settings that can be modified to perform customizations.
4. Right-mouse click Styles and select Create Transform to launch the Transform Creation Wizard.
5. Click Browse... next to the Source folder text field to select the src folder and click OK.
6. In Superclass, browse for the PageByTransform. This will extend the existing transform. 
7. Using the Add... in the Interfaces section, add the LayoutTransform
   Enter the following information for the rest of the text fields:
   Package: ##Any package the developer wants to use##
   Name: ##Any name the developer wants to name the transform##
   Transform description: This transform will change the icon for specific objects in the folder pages.
   
8. Click Next and the java class created should open in the editor.
9. Add the following method to the class:
    
       @Override
       protected boolean isOpen() {
        // TODO Auto-generated method stub
        return true;
       }
   
10. Navigate to Strategy Web Configuration > Styles
    
11. Double click on PageByStyle
12. Using the Change button, select the custom transform created above
13. Save changes
14. Restart Web Server

 
The example provided in this document is provided “as-is” to the user and assumes that the user:

• Can program, compile (e.g. javac, jikes, etc.), and execute Java programs
• Can configure environment variables (e.g. JAR files, property files, etc.)
• Have all the necessary tools to create Java applications (JDK, IDE, etc.)
• Has access to the Strategy SDK documentation.
• Has read the customization warning at the bottom of this document

PREREQUISITES:
 
For the sample to work, the Strategy Web JAR files must be accessible by the Java Runtime
Environment. The Strategy Web JAR files can be found under:

• Strategy Web Universal (JSP): {web_root}/WEB-INF/lib directory.
• Strategy Web (.NET): Program Files\Common Files\Strategy directory.

Note:
 
More elaborate programs will require additional library files and are out of the scope of this document.
 
ADDITIONAL INFORMATION:
 
The Strategy SDK allows you to customize the standard Strategy Web interface, and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy Web products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy Web architecture or the process of customizing Strategy Web, please refer to Strategy Developer Zone (https://resource.microstrategy.com/msdz/).
 
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@microstrategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at http://www.microstrategy.com/Support/ContactUs.asp.
 
 
CUSTOMIZATION WARNING:
 
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.