IBAs, ModeledAttributesDelegate and Workspace limitations

Hello,

in all the years of Windchill projects there is one problem-area that's always coming up:

The (Creo) workspace and it's (annoying) limitations.

Quite often there is a triple set of related objects: CAD Model, CAD drawing and a related item. (yes, that's somewhat simplified 😉 )
Model, drawing and item have usually a different number - which results in the "problem" that in a table view it's hard to group those triple sets or pairs in the table view.
A solution we sometimes use is to define an IBA on the EPM documents named "partno"  as well as on the WTParts. that attribute always contains the value of WTPart.number.

result: in the workspace it's possible to sort by column "partno" and the objects are grouped together. my customers like that.

But... while this is "ok" for smaller installations it's creating a lot of "duplicate" data in the database and especially in the StringValue table which is quite often already huge even without that attribute.

Problems:

Unfortunately the workspaces don't support "local" / alias / calculated attributes for WTParts.
EPMDocuments don't support "locals" anyway.

Local Attributes would be great as it would prevent further increasing the StringValue table.

ModeledAttributesDelegate

The MAD would be great for solving this. But the MAD only processes the EPMs.
The MAD could deliver a PartNo attribute for EPMDocs but not for the WTPart.

Over the years I tried different approaches for this requirement, but it seems to me that the only working way is to define a Global IBA PartNo and add it to EPM and WTPart.
This comes with the huge tradeoff that the systems stores the "WTPart Number" in multiple places and increases the StringValue table...

Has somebody also had this requirement?
Is there a better solution for it?

Thanks in advance!