Ask our Experts
Didn't find what you are looking for? Ask our experts!
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Search in
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-12 12:33 AM
We have some custom metadata fields which allow for easy linking of datapoints to our asset management system. We have a number of templates where all the datapoints of the template have this metadata set via expressions which link to instance parameter field. This works well for us, allowing new instances to be setup and only enter the metadata parameters in one location, and if we add new points to a template then the instances automatically inherit the correct metadata.
However we also want to have some 'add on' templates where we can implement these within an instance. We can setup these add on templates however it currently requires us to set the metadata parameter for these child instances even though it is the same data and fields. So my question is, is there anyway to reference the parameters of the parent?
I hope this made sense. I have also included some simplified print screens to hopefully illustrate what im trying to achieve.
For reference we are running EcoStructure Geo SCADA Expert 2023 November 2024 Update (Build 86.9098)
I also thought I would add that I found the below posts which on one side sounded like it may be doable and the other front that it is a feature under consideration
".Name" as the default Parameter value - Schneider Electric Community
Template Inheritance - Schneider Electric Community
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-24 08:41 PM
From your links, the first one hasn't yet been implemented, and the second link is talking about Animation Parameters in ViewX Mimics (that are part of a Template).. whilst I think you're referencing Template Parameters right (i.e. Parameters configured on a Template that are evaluated when instancing the Template)?
My understanding is that the Template Parameter expressions are still retricted to ONLY reference the configured Parameters against the Template...
I've often used ST Logic, or a ViewX VB script to do the config that you mention. It's not ideal though, since that's another thing to maintain and get issues with.
You could raise an 'Idea' in this forum about having something like a 'run once on object configuration change' kind of thing, that could reference its parents / objects around it to configure its own properties.
The issue with having this all part of the Template Parameters system is that what if there are multiple templates all being deployed at the same time, how to resolve which Template Parameters should be calculated before others? The current system avoids this, since Template Instances only care about their own Parameters.. which don't reference anything else in the tree (so can't have inverted dependency graphs).
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-24 08:41 PM
From your links, the first one hasn't yet been implemented, and the second link is talking about Animation Parameters in ViewX Mimics (that are part of a Template).. whilst I think you're referencing Template Parameters right (i.e. Parameters configured on a Template that are evaluated when instancing the Template)?
My understanding is that the Template Parameter expressions are still retricted to ONLY reference the configured Parameters against the Template...
I've often used ST Logic, or a ViewX VB script to do the config that you mention. It's not ideal though, since that's another thing to maintain and get issues with.
You could raise an 'Idea' in this forum about having something like a 'run once on object configuration change' kind of thing, that could reference its parents / objects around it to configure its own properties.
The issue with having this all part of the Template Parameters system is that what if there are multiple templates all being deployed at the same time, how to resolve which Template Parameters should be calculated before others? The current system avoids this, since Template Instances only care about their own Parameters.. which don't reference anything else in the tree (so can't have inverted dependency graphs).
Link copied. Please paste this link to share this article on your social media post.
You’ve reached the end of your document
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.