Obsoleting Tags From a DataSet (version 24)

Tags are obsoleted from a DataSet by modifying the Canary Collector the data is coming from (depending on the Collector*) or through the Historian.

*If using the Logger (OPC DA) or the OPC Collector (OPC UA), tags can be removed from the logging session. Once these changes are applied and logging resumes, a new file will be created in the DataSet that no longer contains the deleted tags.

If using the MQTT Collector, the user can check the box to "Sync historian tags" when configuring the Subscription settings. With this checked, tags will be automatically removed from the DataSet based upon the messages the Collector receives through the MQTT broker.

If a Collector does not have the ability of obsoleting tags, the following steps can be taken to obsolete them through the Historian interface:

1. Remove the tags from the logging source. Tags being actively logged cannot be obsoleted from the DataSet.
2. Open the Canary Admin client and navigate to the Historian tile
3. Select the appropriate DataSet, and navigate to the most recent HDB file.
4. From within the HDB file, filter the tag list for the tags you wish to obsolete and download the list as a CSV file by selecting the downward arrow icon right of the filter box  
5. Uncheck the 'Include parent path' feature 
6. Save the file locally
7. Within the Historian tile, navigate back to the view of all DataSets
8. Highlight the DataSet you wish to obsolete tags from and select the down arrow icon from the 'DATASET' window, then choose 'OBSOLETE TAGS'
   
9. Upload the CSV file with the list of tags you wish to obsolete and click 'ok'

Remember, tags cannot be obsoleted if they are still being actively logged. You must stop logging on all tags you wish to obsolete prior to trying to remove them.

If the process is not successful, a .txt file will be generated with the reason the tags were not obsoleted.  That file will be created in the same folder as the CSV file you uploaded.  

The obsoleted tag(s) will appear red in the active HDB file and immediately removed from any client browsing.  Upon the start of a new HDB file, the tag(s) will no longer be listed.  You may manually force the rollover of the current HDB file if you wish to verify.