System Tags: Do’s and Don’ts

As intuitive and user friendly as FIN Stack is, there are a few things when it comes to tagging that you do not want to do. These things can cause problems in the database such as something not appearing correctly or data not updating.

System Tags

When using System Tags, here are some that you should avoid. If these tags are on any of your points or other locations, you may experience weird issues or break things.

  • site
  • building
  • floor
  • equip
  • schedule
  • program
  • note
  • weather
  • rule
  • alarm (potentially to be allowed soon with sensor tag, for now you can use alarmPoint or something similar)
  • any of the conn marker tags
  • topLevel

Connector Tags

Below is a list of other connector tags to avoid when bringing data into FIN Stack. You can add them afterwards.

  • Room - if a point is tagged as "room" and trying to import into FIN Stack, an error will be thrown that it can't due to that tag.

Special Characters

There are some special characters that are supported but others that are not. The following characters are supported:

  • a-z, A-Z, 0-9
  • -(hyphen)
  • _ (underscore)
  • , (comma)
  • : (colon)
  • . (period)
  • ~ (tilde)
  • % (percent)

These characters are supported but keep in mind the value doesn't update in Flash DB Builder view when viewing it. You’ll have to refresh the equip to see updated value. The value does update in HTML views such as Point Graphics, Graphics, etc.

  • () (parenthesis)
  • ' (apostrophe)
  • & (and)
  • # (pound)

The following special characters are not supported. Do not use them when naming things. They can break things, not allow the points to update or refresh when viewing. You can use the Search and Replace feature to mass remove those special characters.

  • / (forward slash)
  • ` (acute/grave accent)

Missing sensor/sp/cmd tag

Sometimes customers might remove one of the needed tags for points. Each point has to have either sensor, sp, or cmd tag. If you have more than one of those, you can use this tool to fix it: Fix Conflicting Tags.

You can dive into more FIN related documentation on our Wiki here.