Hi Jan,
I personally would rename them, cause I like standardized naming of properties. But I understand the argument that you don´t want to touch too many Methods.
I assume the way PolyItems are built is a core feature, so we probably cannot directly influence it.
Some more technical approaches (not tested!!!):
Poly-ItemTypes are not real physical ItemTypes/tables. They are just SQL Functions that do a UNION of the various tables.
Idea #1: Change the function in SQL directly.... Ok, I am not sure if it´s possible at all. And of course it´s a modification that is overwritten all the time when you edit the ItemType. And it´s not visible for the Aras update team so if you don´t overwrite it, they definitely will. It´s not the best idea to be honest.
Idea #2: Make a custom SQL view and link it to your target ItemType via "onGet" server Method.
These ideas shall not be seen as final answers. I am also interested in this question! One of design mistakes of the early days of innovator was the name/title inconsistency. Regular Items often use the "name" property, while everything related to CM use "title" as naming field. Building PolyItems with these kind of ItemTypes creates exactly the problem you described.
Out of interest I made a quick SQL test by myself, and indeed a custom SQL call for the Poly could be used to link non-identical property names:
SELECT TOP(10) item_number, name from innovator.Part
UNION
SELECT TOP(10) item_number, title from innovator.EXPRESS_ECO
But as mentioned before, there are maybe better solutions out there. Maybe the "Morphae" ItemType contains some secrets that we haven´t discovered yet, not sure. There is also this TechTip which maybe helps: https://community.aras.com/b/english/posts/tech-tip-sync-a-poly-itemtype-s-properties-with-its-poly-sources
Angela
Edit: The SQL approach will of course eliminate the permission model if you don´t include it into the SQL query by yourself. So it´s not the most secure variant.
You mentioned an onAfterGet approach. It´s not unlikely that some approach with onGet/onBefore/onAfterGet can work. Hope anyone knows more :).
