Hello, I am currently writing an object that is derived from another object because it is a more specialized version for a specific base station. I added a new ParCfgXyz to my new object and parameters in the OOD. I use the base object as BaseRevId inside the OOD and it nicely pulls in all the content into OES next to the new content of my derived object. Now my problem is with the export templates. I need to add a StartupParams.otd for my derived object so I can assign the new parameters. But how can I gracefully call the StartupParams.otd from my base object? <%T= ..\..\..\..\..\Std\Objects\BaseObjectName\V1.0\Export\StartupParams.otd %> This works but it is not very pretty and it relies on both derived and base object having a somewhat exact relative path to each other. Maybe there is a more elegant way? The derived object does not define a new extension so OES automatically executes the extension export template from the base object, which is nice. In the case of the StartupParams, because the derived objects specifies its own StartupParams, the base object's version is considered overriden by OES. Is my understanding of this process correct?
... View more