Choice Fields with Parent Values

The June 2026 release introduces an important enhancement to Choice fields in OnePlan, allowing values to be structured with parent relationships.

This update addresses a common configuration challenge—where similar or identical values previously needed to be duplicated across different contexts—and replaces it with a more streamlined, organized approach.

What’s New: Parent‑Child Structure for Choice Fields

Choice fields can now support parent values, allowing related options to be grouped together instead of duplicated across separate categories.

Key Improvement

• Consolidated Values
  Choice values no longer need to be repeated for different parent contexts (such as project status, primary platform, etc.)

Example: Instead of duplicating the same values under multiple sections:

• “In Progress” (Project Status)
• “In Progress” (Platform Status)

You can now:

• Define a parent category
• Reuse a single value structure across relevant contexts

Why This Matters

Previously, supporting multiple contexts required:

• Duplicating values across fields or sections
• Maintaining consistency manually
• Updating multiple entries when changes were needed

This often led to:

• Inconsistent data
• Redundant configurations
• Increased administrative effort

With parent-supported choice fields, these challenges are significantly reduced.

How This Helps You

1. Elimination of Redundant Values

You no longer need to create and maintain duplicate values for similar concepts across different areas.

Result:
Cleaner configuration with fewer opportunities for inconsistency.

2. Easier Maintenance and Updates

When values need to change (e.g., renaming a status), you can update them in a more centralized way.

Result:
Less manual effort and reduced risk of missing updates in multiple places.

3. Improved Data Consistency

By consolidating values under a shared structure, you ensure that users are selecting from standardized options.

Result:
More reliable reporting and better alignment across teams and plans.

4. More Structured and Scalable Configuration

As your environment grows, maintaining multiple duplicate value sets becomes difficult. Parent-child structure creates a more scalable approach.

Result:
Configurations that are easier to expand and manage long-term.

5. Better Alignment Across Use Cases (BD Context)

For organizations like BD managing multiple classifications (e.g., status types, platforms, categories), this allows:

• Shared terminology across different areas
• Logical grouping of related values
• Reduced configuration complexity

Result:
More cohesive data models without sacrificing flexibility.

When You’ll Notice the Biggest Impact

This update is especially valuable if you:

• Previously duplicated values across multiple fields or categories
• Manage complex classification structures (e.g., status, platform, priority)
• Maintain large or evolving choice lists
• Need consistent values across reporting dimensions

Final Thoughts

Choice Fields with Parent values may seem like a behind-the-scenes improvement, but they deliver meaningful benefits for both administrators and end users.

By eliminating redundancy and introducing a more structured approach, this update helps ensure that your configurations are cleaner, more consistent, and easier to manage over time.