Using Cascading Choice Fields and Grouping to View Business Unit-Specific Data in OnePlan

Overview:
BD has more than 12 Business Units (BUs) using the OnePlan system. To maintain data clarity and avoid exceeding the field limits, we have implemented cascading choice fields based on the Business Unit/Group (BU/Group) field. This article explains how the cascading configuration works and provides a workaround to group and filter portfolio views more effectively.

Why Use Cascading Choice Fields?

To avoid duplicating choice fields for each BU/Group and to ensure data integrity:

• Cascading logic is used.
• The BU/Group field (which is required during project creation) determines the available choice values.
• Each BU/Group sees only its own set of values for cascading fields such as Project Status, Primary Platform, etc.

Known Limitation

Currently, OnePlan’s filter functionality does not restrict the available values in the filter pane based on the selected BU/Group. This may lead to confusion when filtering or grouping data, as users might see duplicate values, or values that do not apply to their BU.

Workaround: Group by BU/Group and Choice Field

To create a meaningful grouped view, follow these steps:

1. Apply a Filter Without Hierarchy

• Navigate to the Portfolio page.
• Click on the Filter icon.
• Choose Add Filter if needed.
• Unselect the “Show hierarchy” checkbox.
• Apply any filters required for your scenario.

2. Set Up Grouping by BU/Group and Choice Field

• Click on the Group icon (see red box in the screenshot).
• In the Group settings:
  • Type and select Business Unit/Group.
  • Type and select the desired choice field (e.g., Project Status).
• Click outside the dropdown to refresh the view.

Your portfolio view will now:

• Group projects first by Business Unit/Group.
• Then, within each BU group, show projects grouped by their corresponding Project Status (or other cascading field).

Visual Reference

Additional Notes

• Ensure you populate the BU/Group field when creating new projects, otherwise the cascading logic will not apply.
• This workaround provides a clearer and more organized way to review BU-specific project data without exposing unrelated choice values.