Adding more persisting tags

You may add two optional properties to the NiagaraNetwork Property Sheet. These two properties specify additional remote tags to pull from the remote station to the Supervisor and persist on the corresponding proxy points (or virtual components).

You are working in Workbench and are connected to the client side station (usually your Supervisor station). Each remote station has one or more tags assigned to its components.
Note: For any specified tag to be successfully fetched from the server-side station to the client-side station, the tag must be assigned to components on the server-side station.
  1. Expand Config > Drivers, right-click the NiagaraNetwork and click Views > AX Slot Sheet
    The Slot Sheet opens.
  2. To add slots, click Slot Sheet > Add Slot (menu).
    The Add Slot window opens.

  3. Give the slot the name tagsToFetch with the Type of baja:String, and click OK.
    This creates a dynamic property.
  4. Create a second dynamic property with the name persistVirtualFetchedTags and Type of baja:Boolean.
  5. Back on the Property Sheet, enter the full tag for each tag to fetch using the syntax: tagDictionary:tagName.
    The tags may be on proxy points and virtuals.
    CAUTION: Fetching tags that override valid implied tags on the Supervisor proxy point can cause confusion and unintended results. For example, it would not make sense to fetch certain implied tags such as the n:type tag because that would override the appropriate n:type tag already implied on the Supervisor proxy point. 
  6. Set persistVirtualFetchedTags to true.
    This property defaults to false. When set to true, the driver adds any fetched tags under the level of this property’s container as properties (read-only) on the virtuals. Essentially, this means they are stored as direct tags on the virtuals.