Derived Property behavior with stereotype generalizations

[joshua.shreve@philips.com]

I am working with automating the updates for profiles, diagrams, validators, and element collection for document generation from a single content source using a plugin. So far I have a lot of progress autogenerating derived properties to create relevant element data to use in constraints, tables, etc. to assist this capability. I have run into one major issue that I can't find the solution to.

I have separate derived properties that need to be identically named to allow element navigation. I am creating a derived properties with the same name but different expressions on two element stereotypes (element 1 and element 2) using customizations. The works excellently except where element 1 is a generalization of element 2 (or vice versa). When I check the derived property value for the inheriting element (element 2) it only applies the derived property expression from element 1. The documentation mentions derived property merging, but I don't see that happening at all so I'm assuming it only merges the properties, not content within the properties.

Is there a setting I am missing or a way to merge or redefine the derived property for the inheriting element? If not, is there another work around? I need the property to be identically named for every other automated aspect of process to work properly. Any assistance would be appreciated.