In Strategy Mobile 9.x and 10.x, users can use URL API to change Group By element through a Report Services Document
Syntax:
Argument | Description |
evt | 2048001 – executeRWDocument. Executes the report services document specified by the documentID argument |
src | The page component that should handle the action and the event |
documentID | Specifies the ID of the report services document to execute |
execFlags* | Flags to be used while executing a document |
msgID* | Specifies the ID of an in-memory report services document. If present, the report services document is fetched from memory rather than executed |
groupByElements | The elements that are going to be passed in the URL. |
GroupByElements Parameter
- groupByUnitGUID: Unique identifier of the attribute. Specifies the groupBy node by matching the attribute in the selector.
- groupByUnitType: Constant value determined by the type of the attribute used in the selector. For the case of regular attributes this UnitType is equal to 12. For consolidations is equal to XX.
- groupByUnitElementID: Long Element ID display from of the attribute. This is the only supported attribute display form so far. Short ElementID or any other display will not work. Specify the value to be selected in the groupBy node.
The matching of the group by nodes is by based on the attribute used in the selector thus the order of the attributes doesn’t matter. If there is no groupBy node in the target for the attribute specified, that groupByUnit is ignored.
If one or more of the group by nodes do not have an attribute element specified, their currently selected element should be set as desired
Macros:
In order to get the values for all the parameters the document designer can make use of certain macros. These macros will resolve at execution time with the appropriate value according the information populated on the RSD dataset.
- groupByUnitGUID -> {&Attribute@GUID}
- groupByUnitElementID-> {&Attribute@LongelementID}
Example: {&Year@GUID};12;{&Year@LongelementID}
NOTE: When using macros please be careful if used with filters or prompts at same time – these may restrict the information retrieved from the warehouse. The worst case scenario will be when no data is retrieved thus the macros will not resolve. In consequence the link functionality will be affected.
Examples:
J2EE:
mstrWeb?evt=2048001&src=mstrWeb.2048001¤tViewMedia=2&visMode=0&documentID=E06C0CE349545B7DBD51BAA6EDEA3E6C&groupByElements={&Year@GUID};12;{&Year@LongelementID}^8D679D4B11D3E4981000E787EC6DE8A4;12;8D679D4B11D3E4981000E787EC6DE8A4;12;BB:8D679D4B11D3E4981000E787EC6DE8A4:1:2:0:2:1:3:2:Mid-Atlantic
mstrWeb?evt=2048001&src=mstrWeb.2048001¤tViewMedia=2&visMode=0&documentID=E06C0CE349545B7DBD51BAA6EDEA3E6C&groupByElements={&Year@GUID};12;{&Year@LongelementID}
Main.aspx?evt=2048001&src=Main.aspx.2048001¤tViewMedia=2&visMode=0&documentID=E06C0CE349545B7DBD51BAA6EDEA3E6C&groupByElements={&Year@GUID};12;{&Year@LongelementID}^8D679D4B11D3E4981000E787EC6DE8A4;12;8D679D4B11D3E4981000E787EC6DE8A4;12;BB:8D679D4B11D3E4981000E787EC6DE8A4:1:2:0:2:1:3:2:Mid-Atlantic
Main.aspx?evt=2048001&src=Main.aspx.2048001¤tViewMedia=2&visMode=0&documentID=E06C0CE349545B7DBD51BAA6EDEA3E6C&groupByElements={&Year@GUID};12;{&Year@LongelementID}