Proposed solution: allow the Key Value (Primary) field in a Key Schedule to be set as a shared parameter (similar to the shared-parameter support added for schedules in Revit 2022). If the primary key value can be a shared parameter, teams could (1) assign parameter values via Key Schedules and then (2) tag those same elements using the primary key value directly without needing workarounds.
This would improve schedule-to-tag consistency and make Key Schedules more useful for categories like Rooms that don't have types. Example: when using a Room Finish Key Schedule where the primary key represents a finish set, users could tag rooms directly with that finish-set value (and/or use it in downstream documentation), rather than needing to concoct a workaround because the primary key cannot be shared or tagged, and shared parameters can't be calculated values within a project.
