Applying filters
You can embed a stand-alone filter in dimensions or query subjects, but if you want a different usage for each embedded filter, you must create different versions of the stand-alone filter. Otherwise, your users could be required to fill in a prompt that you thought was optional if there is any instance where the usage is set to mandatory. For information about mandatory and optional prompts, see Mandatory and optional prompts.
For example, in query subject A, you embed a stand-alone filter and define it as optional. In query subject B, you define it as mandatory. When your users create a report that uses both query subjects, they are required to choose values in both filters, even the one defined as optional. All instances of the filter are considered to be mandatory when used in the same query. The solution is to create different versions of the filter, each with its own name.
To apply a filter after it was created, do the following steps:
- Select the filter, and click Actions, Edit Definition.
- Click the Filters tab, and drag the filter that you created to the Filters box.
- Select the Usage value for the filter.
- Always
- Use this usage value to ensure specified data is filtered out of all reports. For example, your company may have obsolete information that it stores but does not want to report on. This is the default usage value.
- Design Mode Only
- Retrieves a small subset of the data for the sample report. Use this usage value when you do not need to see all the data, for example when testing a query subject.
- Optional
- Specifies that the filter is optional. The user is prompted to filter data and can leave the prompt blank. If the prompt is blank, Framework Manager ignores the filter and retrieves all data for the dimension or query subject.
If you want to view the SQL, click the Query Information tab.