Just wondering if this sounds reasonable.
I currently have script that creates a Tag Path, History and POST dataset. I'm wondering where would be the best place (if any) to replace the tag name before the POST is sent out with an alias tag name.
The Tag Path has the paths to tags that need to be POSTed.
The History dataset is created with Tag Path dataset and the system.tag.queryTagHistory function.
Then the POST dataset is created by breaking up each row of the History dataset in to JSON format with each of the key values needed. Currently it splits the tag name out of each row in the History dataset.
I can add a custom property Alias Name in each tag and read it with the system.tag.readBlocking function. I was wondering if I could create a forth dataset with all the Alias Name custom property values. Then I could reference it for the tag name when creating the POST dataset instead of referencing the History dataset.
I fear that reading all the Alias Name properties from each tag could cause overhead issues when POSTs are sent out.
Another issue is setting up the Alias Name. I have a script to create UDT instances from a CSV file with the system.tag.configure function but if I need to change the Alias Name custom property, it seems like it would be best to just make that change in the parent UDT as long as they are the same in each UDT instance.