-
Notifications
You must be signed in to change notification settings - Fork 1
3. Parameters and Variables
The query /DMO/ANA_C_PAR_1 uses parameters in the where clause. This means the end user can choose concrete values which should be used as filters. The input help (F4) is derived from foreign key associations of the underlying analytical model (cube view). By default parameters become prompts with mandatory input. With the annotation @AnalyticsDetails.variable.mandatory: false the prompt becomes optional and the user does not need to enter a value for the prompt.
The query /DMO/ANA_C_PAR_INTVL has a hidden parameter, which is a interval variable with low and high value filled with default values. The query is filtered by this parameter.
The query /DMO/ANA_C_PAR_Multi hows the usage of parameters in different contexts. It also shows how the labels of restricted measures fields SalesAmountInTargetCurr, SalesAmountInYear such that the label reflects the input for the variables
The query /DMO/ANA_C_PAR_HIERNODE shows the usage of hierarchy node variables. The hierarchy specified by the association _DepartureAirportHier is used two times:
- the query is filterd by a selected hierarchy node (user input)
- it is used as a display hierarchy
The query /DMO/ANA_C_PAR_Valuehelp shows how to add a specific value help to a parameter. Reasons to use it would be if there is no standard value help available or if the standard value help is not specific enough.
The query /DMO/ANA_C_PAR_DERIVATION shows how to specify dynamic and static default values for a parameter.
The query /DMO/ANA_C_PAR_DERIVATION_1 differs to /DMO/ANA_C_PAR_DERIVATION in such a way, that the parameter P_FirstDayOfMonth is not hidden. Therefore, the derivation is only performed before the prompts are displayed and the prompt is prefilled with the result of the derivation. For performing the derivation the default value of P_FlightDate is used. If the user overwrites the result, the derivation is not performed again afterwards