I was hinting at the fact that he can have internal bindings that point to a single property, as well as scripts that call functions from the central library. This mitigates the need for mass changes in a well planned project, but doesn’t truly satisfy OPs question as Carl’s “template components” will.
Out of curiosity - do you guys have many real world occurrences in Ignition when you need to do the same change(s) to lots of components? Of those, cases where deleting and re-creating from a palette takes much time? It seems to me that mass duplication is usually taken care of with parameter passing (popup windows or selectable objects), so in effect you end up modifying the object in one place. Don’t get me wrong - I’m as interested in this feature as the next guy. It’s the one notable feature that Wonderware has been touting for a few years that other vendors don’t support. I’m curious how useful their implementation is.