Skip to content

[Schema Builder] Entity Reuse: Sync picklist choices to current data #545

Description

@cmrn-rhi

Disclaimer: Generated from 'UX Review - DH Schema Editor (2025)' worksheet tab '2) Heuristic Review' using Claude Code on 2026-06-04; please review to the original sheet for the original human curated version of this information.

ID: 58 | Severity: Major - Action Barrier
Review Status: 3- Ready for Review
Priority: Awaiting dev review
Originally Reported: 2025-09-18 (DH 1.9.8, dh2-1m-rework)

Issue

Picklist "Inherits" function isn't changing the values in "Picklist Choices". When in the Picklist tab applying the "Inherits" metadata (e.g., changing the "anatomical material menu" so that it inherits the "body product menu") the resulting "Picklist choices" are still the original menu (e.g., "anatomical material menu"). As a user, I would expect "Picklist choices" to reflect the updated/changed version and would perceive this as a failure of inheritence.

Goal

Have picklist list choices reflect the user's current data.

Recommendation

(1) Make it so the "Picklist choices" shows the new menu choices. If inherited menus are not editable than ideally they would be read only (while reflecting the new menu).
(2) If inherited Picklist menus cannot be edited, guidance should reflect that and "Picklist choices" should (ideally) be read only or not editable when "Inherits" is active so the user gets clear feedback that they cannot perform these actions.
Additionally, it should be made clear in the guidance if inherited menus automatically update when the source menu changes. Example: menu-2 inherits menu-1's picklist; menu-1's picklist is updated; does menu-2 update to reflect changes to menu-1 or does it keep the original instance?

Related Issues

#482
#520

Issue Screenshot / GIF

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    UXUser Experience related issue

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions