At a risk of sounding stupid...
The historical tag provider originating connection names are stored in the internal DB. Could you cache this? Obviously using an API method to get this would be better, but in a pinch..
At a risk of sounding stupid...
The historical tag provider originating connection names are stored in the internal DB. Could you cache this? Obviously using an API method to get this would be better, but in a pinch..