Summary

When navigating between OTBI analyses using Action Link → Navigate to BI Resource, only a subset of prompt types are automatically mapped to destination analyses using Is Prompted. Column prompts using the Between operator are not reliably passed, resulting in incomplete filter context on the destination analysis.

Current Behavior (Known Gap)

Today, users often design dashboards with a source analysis that includes column prompts (for example, date ranges) and a detail analysis that relies on Is Prompted filters.

Example setup:

• Source analysis
  • Column Prompt:
    • Creation Date BETWEEN :From Date AND :To Date
  • Column: Buyer
    • Buyer column value configured with Action Link → Navigate to BI Resource
    • Target = second analysis
• Destination analysis
  • Displays:
    • Creation Date
    • Buyer
  • Criteria set to:
    • Creation Date → Is Prompted
    • Buyer → Is Prompted

Observed behavior:

• Clicking a Buyer value correctly navigates to the destination analysis.
• The Buyer filter is applied.
• The Creation Date BETWEEN prompt values from the source analysis are not automatically mapped, even though the destination criteria is set to Is Prompted.
• Users must re‑enter the date range manually or rely on prompts instead.

Expected / Desired Behavior

Using the same setup as above:

• When a user clicks a Buyer value in the source analysis:
  • Navigation occurs to the destination analysis.
  • All compatible prompt values are mapped automatically, including:
    • Buyer = <selected value>
    • Creation Date BETWEEN <From Date> AND <To Date>

The destination analysis should open fully constrained by:

• Discrete prompt values (Equals, In, Is Prompted)
• Range‑based prompt values (Between)

This would allow users to preserve full analytical context across navigation without duplicating prompts or rebuilding filtering logic.

Business Impact

• Limits the effectiveness of drill‑through and summary‑to‑detail navigation patterns.
• Forces users to introduce redundant dashboard prompts or custom workarounds.
• Prevents clean, intuitive interactive reporting where context (especially date range) should persist naturally.
• Reduces confidence in Is Prompted as a reliable, generic filtering contract between analyses.

Requested Enhancement

One of the following (in increasing order of usefulness):

1. Enhance Navigate to BI Resource to automatically map all supported prompt operators, including Between, when the destination filter is set to Is Prompted.
2. Provide explicit control to enable/disable mapping of range‑based prompts.
3. If range prompt mapping is not supported by design, document this limitation clearly in OTBI navigation and prompting documentation.