(Perspective)
I have a large array of data and some of the values have transforms on them. When dragging the tag to the component, the transform gets blown out. I want to keep all the existing configurations and just replace the tag. Is this even possible?
More information required.
Just rebind the tag in the binding editor instead of dragging it on. Or you could use find replace
Dragging a tag onto a prop to bind it will replace the binding entirely, as you've discovered. It will also replace the binding with the default bidirectional value too (off? From memory) which may or may not be what you want.
Yeah I was just looking for a more time efficient method to do since I have a boatload of them where the only difference in tags is a number (ie, CH1, CH2, CH3…), and there’s no find/replace on a selection, only globally.
There is actually, as long as you’re on a version from the last year or two. It’s a bit funny to use though. Select your views and then right click and you should see “find in selected” or similar. If you’re selecting multiple, then the views need to be closed (this is the “funny” part).
Alternatively, you’ve also always got the option to modify the underlying view json file directly. A “boatload” might be better suited to this type of approach via a script to bulk make the edits. AI would handle this well
That’s for views. I want to find/replace tagnames in components within a single view.
In Rockwell, this would be like selecting a bunch of items and hitting Ctrl-R. In Wonderware, it’d be like selecting items and hitting Ctrl-E. Only replace what’s selected, very powerful and important feature for HMI development. I’m sure Ignition will add it eventually; but I’m very surprised it doesn’t exist natively yet.
This honestly isn't a feature I have ever wanted in Ignition. Ignition has superior tools and tricks that mean you don't need manual tools like selection based find and replace.
This is super easy, just make a parameter or custom property that contains the number, then indirectly bind all the other bindings based off that number. Copy the component, change one number exactly once and its fixed. No dependence on find/replace at all, and super easy and fast to maintain.
Normally when I see complaints like this, it's because the person complaining is still so used to the legacy platforms that they don't immediately see the other ways of dealing with the task. Normally its a bit of a "zoom out" solution, rather than finding the exact replacement for a method on a different platform, zoom out a bit and look at the actual problem you are solving and then look at possible ways to approach it with all the tools available.
Also I'm constantly impressed with the range of solutions that people here in the forum have come up with given the same larger problem.