In the Niagara History Export Manager you can use “NiagaraSystemHistoryExport” descriptors to export locally-sourced histories. This allows you to export many histories at once, instead of individually exporting them “one at a time.” For this to work, local history extensions (for histories to be exported) must be configured with “System Tags” property values. Refer to the NiagaraAX User Guide section “Configure history extensions” for related details.
Instead of using the export manager’s “Learn Mode” (Discover) to add history export descriptors, you manually add new descriptors in the Niagara History Export Manager, by selecting NiagaraSystemHistoryExport in the “Type” drop-down control of the New popup dialog, as shown in Figure 110.
In the resulting New dialog for the system history export descriptors, you enter one or more “System Tags” as a text pattern, as shown in Figure 111.
Figure 111. Enter “System Tags Pattern” text to match local history extensions’ “System Tags” values
You can enter multiple System Tags in this “System Tag Patterns” property, using a semicolon (;) as delimiter between System Tags. In addition, you can use an asterisk (*) as a “wildcard” when entering System Tag values. In the Figure 111 example, the System Tag Patterns value is:
Lon;Occ*
In this example, any local points with history extensions configured with System Tags property values of “Lon” and/or a value beginning with “Occ” will be exported after this is added and executed.
For example, history extensions with a System Tags property value of “Lon”, “Occupancy” or “OccUnocc” will be included, but ones with a System Tags value of only “OcUnoc” or “Lon1” will not. Note that the Execution Time property values apply to all associated exports, and operate the same as for regular NiagaraHistoryExport descriptors. See Niagara History Export properties.