Issue
History Extensions in History Service show a “Fault” Status. The Fault cause displays: "Duplicate history id:" followed by the name of the object.
Environment
I/A Series G3, version 3.3.22 and later
Cause
By default, history extensions inherit the name of the objects they’re attached to (e.g. CFM). If CFM is to be trended on multiple VAV units (VAV1, VAV2, etc.), this can cause issues when enabling history collection in the History Service; one or more histories will be in a “Fault” state, with the error message: “Duplicate history id:” for the Fault Cause.
Resolution
To resolve the issue, the history names can be configured to include the parent folder names:
1. Open the Program Service in the station’s Services container, and click on the “Find Objects” button at the bottom of the Batch Editor view
2. In the Bql Query Builder window, select (Custom Type) in the “Of type:” drop-down menu. Two more drop-down menus will appear. In the middle drop-down, select “history”. In the last drop-down, select the appropriate history extension (e.g. NumericIntervalHistoryExt). Then, click OK. The Batch Editor view will populate with all of the history extensions in the station for the extension type selected
3. In the Batch Editor view, highlight all of the history objects, then click the “Edit Slot” button at the bottom of the view
4. In the Edit Slot window, select “historyName” in the Property drop-down menu. In the New Value field, type the following:
%parent.parent.name%_%parent.name%
NOTE: Depending on the tree structure, the filter may need to be modified in order to create a unique history name. For example, if the network is structured in the following format:
In this example, the object nviSatSwitch1_value is a child of the Points container, which is a child of the device MnlRs3_10. In order to create a unique name for the history extension, the correct filter would need to be:
%parent.parent.parent.name%_%parent.name%.
5. Click OK. After a few seconds, the BatchEditor Results window will appear, displaying the objects that were changed. The history extensions now have unique names, and can be enabled in the History Service
