In Strategy 9.x and 10.x, users can use the following syntax to change page by element using Mobile URL API.
Syntax:
Argument | Description |
evt | 4001 – ReportExecuteEvent Allows users to execute reports |
src | The page component that should handle the action and the event |
reportViewMode | Grid (1) or Graph (2) mode |
reportID | Specifies the ID of the report to execute |
execFlags* | Flags to be used while executing a report |
resultFlags* | Flags to be used while retrieving the report results |
pageByElements | ;;^ ;; |
*Optional parameter
PageByElements Parameter
- pageByUnitGUID: Unique identifier of the attribute. Specifies the pageBy node by matching the attribute in the selector.
- pageByUnitType: 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.
- pageByUnitElementID: 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. Specifies the value to be selected in the pageBy node.
The matching of the pageBy nodes is by based on the attribute used in the selector thus the order of the attributes doesn’t matter. If there is no pageBy node in the target for the attribute specified, that pageByUnit is ignored.
If one or more of the pageby nodes do not have an attribute element specified, their currently selected element should be set as desired
Use of 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.
- pageByUnitGUID -> {&Attribute@GUID}
- pageByUnitElementID-> {&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.
Example
+ J2EE:
mstrWeb?evt=4001&src=mstrWeb.4001&reportID=C578192B428AC0387FA5B3A3E02C3E78&reportViewMode=1&pageByElements={&Year@GUID};12;{&Year@LongelementID}^8D679D4F11D3E4981000E787EC6DE8A4;12;BB:8D679D4F11D3E4981000E787EC6DE8A4:1:2:0:2:1:3:16:Sports & Health
mstrWeb?evt=4001&src=mstrWeb.4001&reportID=C578192B428AC0387FA5B3A3E02C3E78&reportViewMode=1&pageByElements={&Year@GUID};12;{&Year@LongelementID}
Main.aspx?evt=4001&src=Main.aspx.4001&reportID=C578192B428AC0387FA5B3A3E02C3E78&reportViewMode=1&pageByElements={&Year@GUID};12;{&Year@LongelementID}^8D679D4F11D3E4981000E787EC6DE8A4;12;BB:8D679D4F11D3E4981000E787EC6DE8A4:1:2:0:2:1:3:16:Sports & Health
Main.aspx?evt=4001&src=Main.aspx.4001&reportID=C578192B428AC0387FA5B3A3E02C3E78&reportViewMode=1&pageByElements={&Year@GUID};12;{&Year@LongelementID}