Enable reliable cross-dimensional MDX context propagation in PAW selectors and subset editor (dependent / cascading selectors)

Dear team,

Description:
In IBM Planning Analytics Workspace (PAW), dynamic MDX expressions that rely on CURRENTMEMBER, PROPERTIES, or attribute-/hierarchy-driven logic from another dimension work correctly in Cube Views, but behave inconsistently in the Subset Editor and Selector components within Workbooks.

Current Behavior:

Cross-dimensional MDX (e.g. [Planstelle] selection driving [Kostenstelle] via attributes or hierarchy relationships) evaluates correctly in Cube Views.

In Subset Editor and Selector widgets the same expressions frequently result in:

• Empty sets

• Stale or non-updating results

• Missing synchronization when a related title dimension changes

IBM Support has confirmed that selectors and the subset editor evaluate MDX outside of full cube context and only react to direct user interaction.

Expected Behavior:

• Consistent MDX evaluation across Cube Views, Subset Editor, and Selector components

• Reliable context propagation between title dimensions in PAW Workbooks

• Automatic updating of dependent / cascading selectors based on attributes, hierarchies, or mapping relationships

Business Impact:

This limitation significantly restricts the development of modern, user-friendly planning applications in PAW.

Cascading and dependent selectors are a standard requirement in most planning models (e.g. Cost Center ↔ Position, Product ↔ Category, Version ↔ Time, etc.).

As a result, customers are forced to implement complex workarounds (control cubes, TI processes, etc.) or move important logic to Planning Analytics for Excel. This increases development effort and reduces maintainability and usability.

Requested Enhancement:

• Full cube context propagation to selectors and the subset editor

• Consistent cross-dimensional MDX evaluation across all PAW components

• Native support for dependent selector synchronization in workbooks

• Optional framework to explicitly define selector dependencies within a workbook

Use Case Example:

Selecting an element in the Planstelle dimension should dynamically drive the subset of the Kostenstelle selector via attribute or hierarchy relationship.

The Kostenstelle selector must update automatically when both dimensions are placed in the title area of a PAW Workbook.

Conclusion:

This enhancement would significantly improve PAW’s capabilities for enterprise planning applications and align it with common design patterns in modern planning and BI systems.

Thanks in advance!

With best regards,
Vitalij