Indirection adjustment approaches for changing tag naming standards

Ignition
1

Here's sort of a general question I have as I rationalize specifications from my clients and multiple integrators in the Solar/BESS SCADA space. Any best practices or creative solutioning?

Let's say an integrator has a standard tag naming convention for their product, where a device type of typeA has members A1, A2, A3, etc. Obviously much more complicated than that since these facilities usually have hundreds of thousands of tags, but the concept is straightforward. Now let's say they have view viewA which indirects everything based on a param tagPath=instanceOfTypeA.

Now let's say some clients are getting much more particular about their namespace and are providing tag naming schemes for their facilities. I would therefore assume there would be a major renaming/remapping of indirected references below tagPath=instanceOfTypeA, a significant amount of rework, testing, and risk to maintain the same Perspective screens for a new client's tag naming specifications.

Any shortcuts to both accommodate the client's tag naming conventions while still preserving the integrator's thousands of instances of indirection in scripts and views?

2

One idea I had was having the deployment automation write the original standard tagPaths to a custom property, and then using something like globalVarMap or a script to write a lookup table to a custom property in the root of the UDT instance. This would still require reworking every instance of indirection in scripts and views, but at least could provide a framework for easy rework from client to client. This also sounds like it would be a significant performance hit versus native indirection. But I'm hoping for something even simpler.