By filtering data in a Dive, rather than defining the filter directly in a cPlan, you can better control the use of the QuickViews by multiple portlets on a DivePort page. When you define a QuickView Set and place it on a DivePort page, all portlets automatically apply those QuickView filters. It is possible to configure a portlet to not respond to a certain QuickView in the set. The trick is to acknowledge the QuickView parameter, and then ignore it.
When you use Dive files, you can take a parameter from the QuickView Set and then do nothing with it. In other words, to control which QuickViews each portlet uses when displaying data, configure your Dives so that they do the filtering, rather than defining the cPlans beforehand with filtering.
For example, suppose a QuickView Set defines three QuickViews. One Dive uses the three QuickView parameters as filters, while the second Dive takes those same QuickView parameters, but uses only one as a filter when it invokes the cPlan.
The code for the first Dive could resemble the following
dive {
take-parameter "Year" {
default "16-17"
}
take-parameter "Campus" selection=true {
default-all-values
}
take-parameter "Faculty" selection=true {
default-all-values
}
cplan "EnrollmentAge.cplan" {
filter `param_match("Year","Year")`
filter `param_match("Campus","Campus")`
filter `param_match("Faculty","Faculty")`
pass-parameter ...
}
window {
...
}
}
And the Dive using only one QuickView value
dive {
take-parameter "Year" {
default "16-17"
}
take-parameter "Campus" selection=true {
default-all-values
}
take-parameter "Faculty" selection=true {
default-all-values
}
cplan "EnrollmentAge.cplan" {
filter `param_match("Year","Year")`
pass-parameter ...
}
window {
...
}
}