Eliminating Mandatory Master-Detail Relationships if same query is tied to page and crosstab/chart

Currently, when the same query is tied to both the page and the crosstab/visualization, the product requires defining a master-detail relationship. While this behavior is consistent across visualizations, crosstabs, and earlier product versions, it introduces challenges from a user perspective.

Key Concerns:

1. Unintuitive Behavior:

   • From a user perspective, the requirement to define a master-detail relationship in this scenario is not intuitive, especially when the master-detail functionality is not being used.

   • Users often expect to be able to assign the same query to a page and populate multiple data containers (e.g., lists, crosstabs, charts) without additional configuration. This is a common reporting technique to simplify report maintenance and reduce complexity.

2. Usability Impact:

   • The need to define a master-detail relationship in this specific case can confuse users and complicate the report design process.

   • Explaining this behavior to end-users is challenging, as it appears unnecessary and inconsistent with their expectations.

Proposed Enhancement:
We propose revisiting the product design logic to remove the requirement for defining a master-detail relationship when the same query is tied to both the page and the visualization/crosstab, provided that the master-detail functionality is not being explicitly used.

Benefits:

• Improved user experience by aligning the product behavior with common reporting practices.

• Reduced complexity in report design and maintenance.

• Enhanced clarity and ease of use for end-users, leading to fewer support queries and training needs.

Business Impact:
This enhancement will significantly improve the usability of the product for report designers and end-users, reducing frustration and improving productivity. It will also align the product's behavior with user expectations, fostering greater satisfaction and adoption.