If a report has the ‘Merge Row Headers’ option disabled, the rows correctly appear unmerged when running the report in Strategy Web 9.x as shown in the following screenshot:
However, when executing the same report using the reportExecute task to return the simplified report XML, the rows are incorrectly showing merged data instead. The parameters used in the reportExecute task are the following:
http://AppServer:8080/MicroStrategy/servlet/taskAdmin?taskId=reportExecute&taskEnv=xml&taskContentType=xml&sessionState=SESSIONSTATEVALUE&styleName=ReportDataVisualizationXMLStyle&reportViewMode=1&reportID=02F6281147D1A5C8D4FA0FA74FAFFBFF
The returning data appears merged:
To get the data in an unmerged fashion, the resultFlag parameter must be added to the task request to include the banding flag. So for example, to include both grid data and to force the data to return unmerged, the flags DssXmlResultBandingStyle and DssXmlResultGrid should be specified which equates to 393216.
The new task API link looks like the following:
http://AppServer:8080/MicroStrategy/servlet/taskAdmin?taskId=reportExecute&taskEnv=xml&taskContentType=xml&sessionState=SESSIONSTATEVALUE&styleName=ReportDataVisualizationXMLStyle&reportViewMode=1&resultFlags=393216&reportID=02F6281147D1A5C8D4FA0FA74FAFFBFF
Invoking this link generates the following results:
For more information about the possible values that can be used in the resultFlags parameter, see the following link:
https://resource.microstrategy.com/MSDZ/MSDL/921/docs/ReferenceFiles/com/microstrategy/webapi/EnumDSSXMLResultFlags.html
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:
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://community.strategy.com/topic/0TO44000000FliLGAS/sdk).
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 https://www.microstrategy.com/en/support/contact-support.
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.
