If you are using a Flex-based Management view, you can configure the corresponding Management view structure file in such a way that a Management view component is used as the filter selection for another component of this Management view. In this case, one Management view component acts as the filter source, another as the filter target.
If you are using a table-based Management view component as the filter source, selecting a row in the table uses the combination of individual dimension values from this row as the filter setting for the dependent filter target component.
Example
The screenshot below shows a table-based Management view as the filter source
Selecting the second table row in the lower Management view component (filter source) sets a dimension filter for the combination of Plant=Oak Springs (3000) and Time=Dec 06 and Material=Machines and Sold-to party=Brazil in the upper component (filter target).
Define interactive filters
Interactive filters for each Management view component are defined using the showMVFlexComponent JavaScript method in the Management view structure file by specifying the identifier of the Management view components to be used as the filter source for this component in the filterMasters parameter.
Combine interactive filters
You can also use multiple filter sources by specifying the identifiers of the filter source components separated by commas. Their order determines the priority - the first filter source component listed has the highest priority.
All filters specified for a Management view component are linked by an AND operator. If multiple filter source components contain filters for the same dimension, only the filter in the filter source component with the highest priority will be used.
To avoid empty result sets when setting filters, you should ensure that setting a filter in the filter source component returns data for the filter target component. For example, if you link two Management view components based on different process type groups for filtering, the result set will always be empty.
Warning
Make sure that the dependency between the filter target and the filter source does not cause any cyclic dependencies between the Management view components.
Example
In the following example of a Management view structure file, for the filter target component with the identifier 0 (Query1) specifying "1,2,GLOBAL_FILTER" for the filterMasters parameter means that in the MV display the component will first adopt the dimension filters set in the filter source component with the identifier 1 (Query2), then filter settings from the filter source component with the identifier 2 (Query3) and finally global filter settings.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd">
<html>
<body>
<script src="../assets/javascript/mvhelper.js"
language="javascript" />
<script src="../assets/javascript/linkhelper.js"
language="javascript" />
<script language="JavaScript" type="text/javascript">
initializeFlex();
</script>
<div id="GlobalFilterDiv" style="position:absolute;
top:0px; z-index:1; width:100%;">
<script language="JavaScript" type="text/javascript">
showMVFlexFilterComponent("GLOBAL_FILTER");
</script>
</div>
<div style="position:absolute; top:105px;
z-index:2; width:100%;">
<table cellpadding="0" cellspacing="0" rules="none"
frame="void" border="0" bgcolor="#FFFFFF"
width="100%" height="100%">
<tbody>
<tr>
<td>
<script language="JavaScript"
type="text/javascript">
showMVFlexComponent("0", "Query1",
"FAVORITES_PRIVATE", "FLEX", "100%",
"400", "1,2,GLOBAL_FILTER", "");
</script>
</td>
</tr>
<tr>
<td>
<script language="JavaScript"
type="text/javascript">
showMVFlexComponent("1", "Query2",
"FAVORITES_PRIVATE", "FLEX", "100%",
"400", "2", "");
</script>
</td>
</tr>
<tr>
<td>
<script language="JavaScript"
type="text/javascript">
showMVFlexComponent("2", "Query3",
"FAVORITES_PRIVATE", "FLEX", "100%",
"400", "", "");
</script>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>