Using the Locations table location fields in OMK apps

For a discussion of the difference between the sysLocation and location node attributes see this article:

Handling different location attributes in NMIS

For Geogrpahic maps to work you need to have created appropriate "location" entries in the Locations table and then configured / assigned the devices with a "location".

To enable the node's attribute "location" (the devices location based on the NMIS Locations table) as one of the Node Selector fields in the Nodes view in opCharts see here:

• Adjusting node slector attributes

There are several other tables in opEvents and opCharts which refer to a nodes location information. 

These will typically refer to the devices "location" attribute not sysLocation. 

If you need to you can adjust (as of version 3.2.2) whether the table refers to "location" or "sysLocation" by altering the table schemas.  To do so find the tables you want to change and alter their schema.  An example would be to find any current use of "sysLocation" and change it to use "location".

## This is an example 
cd /usr/local/omk/lib/json
grep -r "sysLocation"
## Select all the schemas refering to sysLocation to alter
opCharts/table_schemas/opCharts_node-summary-table.json:  "sysLocation",
opCharts/table_schemas/opCharts_node-list.json:  { "name": "node_summary.sysLocation",
opEvents/table_schemas/opEvents_node-ip.json:		"name": "sysLocation",
opEvents/table_schemas/opEvents_node-log.json:    "name": "sysLocation",
 
# edit the file opCharts/table_schemas/opCharts_node-summary-table.json
# change the line "name" from sysLocation to location as shown
  { "name": "node_summary.location",  
    "label": "Location",
    "cell": "String"
  },