Tips & Tricks #7: How to Enable or Disable Match Case Sensitivity for Prompts using MicroStrategy Web
Believe it or not, this is a question I get asked a lot by clients. Based on their requirements or data, many clients do not want the Match Case Sensitivity check box preference enabled to begin with when they are prompted. Fortunately for us, the solution to this is fairly simple as I show below.
If you have a MicroStrategy question you would like me to answer or blog about, please e-mail it to me (include screenshots if it will help) to email@example.com. I will do my best to answer your questions.
Match Case Sensitivity Preference
When you run certain prompt types in MicroStrategy Web, the interface offers a search option followed by a Match Case Sensitivity check box.
This functionality allows users to search for specific elements within the prompt’s available answers. To allow even more flexibility, the check box allows the user to restrict the search results only to those that match the case entered. In the screenshot below, you can see the check box is enabled (checked) and case sensitivity will be matched.
However, you can control whether this option is enabled or disabled by default for all prompts by setting the following preference in MicroStrategy Web.
This option is under Preferences, Project Defaults, Prompts.
Don’t forget to press the Apply button for the changes to take place.
Now, in the screenshot below, you can see the check box is disabled (unchecked) and case sensitivity will not be matched.
This is something that I actually had the opportunity to use this week. It really came in handy and helped satisfy my client’s requirements.
Just a reminder as we discuss this tip, I am using MicroStrategy v9.4.1 and MicroStrategy Developer. Developer is the new name for MicroStrategy Desktop as of v9.4.1
This example demonstrates how to create a 3-level deep nested prompt that will prompt the user to select a year, then a quarter within that year, then a month within that quarter.
Prompt-in-prompt is a feature in which the answer to one prompt is used to define another prompt. This feature is only implemented for element list prompts. The following steps describes how to achieve this.
Create the Year Prompt
- Create the highest level filter first. This is a filter which contains a prompt on an attribute element list. Create a filter on the attribute “Year” and click “Prompt“.
- Click “prompt on attribute element list” and then click “Next” through the rest of the screens to accept the default values.
- Do not set any additional conditions. Save the filter as “Year Filter“.
From this level on, each filter will contain both a prompt on an element list and will have its element list filtered by the filter created one level above it. There is no limit to the number of such filters that can be layered.
Create the Quarter Prompt
- Create a filter on attribute “Quarter” and click “Prompt“.
- Select “Use a filter to reduce the number of elements” and select the “Year Filter” created in the previous step.
- Save this filter as “Quarter Filter” .
Create the Month Prompt
- Follow the same basic procedure as above to create a Month filter. Create a filter on attribute “Month“.
- Click “Prompt“.
- Select “Use a filter to reduce the number of elements” and select the “Quarter Filter” created in the previous step.
- Save this filter as “Month Filter” .
Try it Out
Place only the lowest level filter in the filter section of the report. In this case, the “Month Filter” will be placed in the filter section.
When the report is executed, it will prompt for Year, then for Quarters in the selected Year, then for Months in the selected Quarter, as shown in the following sequence of screen shots.