How-To (User Context)
Last updated
Last updated
This Section provides detailed guide to help in understanding the usage of Parameters based on User Context & steps to create them.
Parameter acts as an independent variable that can be used to display all the dependent items.
Auto-populate the Costcenters based on the Profitcenter selection.
Prerequisite - Defined relationship between Profitcenter & Costcenter with "Linked to Property"
Profitcenter is created as "Linked to Property" in Costcenter field & the complete mapping of Costcenter - Profitcenter is updated as show below -
Profitcenter1 can be mapped to multiple cost centers such as Cost center1, Cost center2) & similarly Porfitcenter2 can be mapped to Cost center3 & Cost center4.
To define the Parameters, Click on +Add Button. & populate the the following information -
Name: Parameter name - Profitctr
Type: Select the type of context - User Context
User Context: If parameter value to read from the user context selected
Fields: Select the field/property - Group Finance - Profitcenter - ID
Relationship: Leaf members
Click on SAVE to save the Parameter, & can be now used for the report.
Sample Field configuration : Model -Group finance & Field - Profit center & Property - ID
Create report definition & refresh report with Costcenter in Rows for display
Select Costcenter member selector using filter Icon
Select Type -Profitcenter (as Profitcenter is linked to dimension for Costcenter)
Parameters defined for this field are listed with format ¶meter name%
Select %Profitctr%
Click Okay & Refresh the template.
Expected output - Template is refreshed based on the Profitcenter from user context
In this case, Profitcenter from user context is 1010, hence all Costcenters mapped to this Profitcenter are populated with Costcenter ID & Description in the report
Change User Context - Change the Profitcenter from User Context to 1030 & Refresh teh report , the expected Outcome as displayed below will be all Costcenters that are mapped to 1030 Profitcenter.
Dynamically display Time members based on the Version selection
Prerequisites: Version has "Linked to Property" to Time & members of Time field are mapped to respective Version member
So, in case Version member is selected, corresponding Time members mapped are also retrieved
example - Version members - ACTUAL, BUDGET & PLAN has the Start year (Linked Property to Time) as a property with Time members mapping populated.
To define the Parameters, Click on +Add Button. & populate the the following information -
Name: Parameter name - Time
Type: Select the type of context - User Context
User Context: If parameter value to read from the user context selected
Fields: Select the field/property - Group Finance - Version - Start Year
Relationship: Leaf members
Click on SAVE to save the Parameter, & can be now used for the report.
Sample Field configuration : Model -Group finance & Field - Version & Property - Start Year
Update Report definition with Time & Version in Columns
Select Time member selector, as this needs to parameterised from context
Select Type -Parent
Parameters defined for this field are listed with format ¶meter name%
Select %Time%
Click Okay & Refresh the template.
Expected output - Template is refreshed based on the Version from user context
In this case, Version from from user context is BUDGET, hence Time mapped to this member are populated with Time ID as 2020 in the report
Change the user context for Version Change the version from user context to PLAN/ACTUAL & refresh to see the Impact of Time members in the report.
Watch the Video for Complete How-To Use Parameters
