After adding a prompt to a relational sourced report it is decided that the consumers require multi- select functionality instead of a single-select. What two modifications must be made to the report?

Question

Options

• AChange the Filter property Multi-select to Yes
• BChange the Cascade source property of the Prompt to represent more than one value.
• CChange the Prompt property Usage to Select-many.
• DChange the Filter expression of the Query from "=" to use "in".
• EChange the Prompt property Multi-select to Yes.

• A
  3% (1)
• B
  10% (3)
• C
  81% (25)
• E
  6% (2)

Explanation

Converting a single-select prompt to multi-select in a relational report requires two coordinated changes: the prompt itself must be told to accept multiple values (option C - setting Usage to "Select-many"), and the filter expression in the query must be updated to handle a set of values rather than a single value (option D - replacing "=" with "in"). These two changes work as a pair because the prompt controls how many values a user can choose, while the filter expression controls how those values are matched against the data.

Why the distractors fail:

• A is wrong because there is no "Multi-select" property on the Filter object in relational reports - multi-select behavior lives on the Prompt, not the Filter.
• B is wrong because the Cascade source property governs cascading prompts (where one prompt filters the choices of another), not multi-select capability.
• E is a common trap - "Multi-select" sounds right, but the actual property name on the Prompt is Usage, set to "Select-many." There is no "Multi-select" property on a relational prompt.

Memory tip: Think of it as a handshake - the Prompt opens its hand to accept many values (Usage = Select-many), and the Filter opens its hand to pass them along (= → in). Both hands must open, or the handshake fails.

No community discussion yet for this question.