Field Exclusion Controls
Overview
Field exclusion lets you hide specific fields from the entity inspector. All fields not explicitly excluded will remain visible.
Key Points
- Only affects what appears in the entity inspector - does not remove data from the visualization
- Cannot exclude essential fields (like node IDs and edge source/destination)
- Type-specific exclusions take precedence over global exclusions
- Useful when you want to show most fields but hide a few specific ones
Examples
Global Exclusion
Hide specific fields from all nodes:
{
  "node_encodings": {
    "bindings": {
      "node": "nodeId"
    },
    "complex": {
      "default": {
        "pointFieldExclusionEncoding": {
          "graphType": "point",
          "encodingType": "fieldexclusion",
          "exclude": {
            "internal_id": true,
            "timestamp": true,
            "debug_info": true
          }
        }
      }
    }
  }
}
Type-Specific Exclusion
Hide different fields for different types of nodes:
{
  "node_encodings": {
    "bindings": {
      "node": "nodeId"
    },
    "complex": {
      "default": {
        "pointFieldExclusionEncoding": {
          "graphType": "point",
          "encodingType": "fieldexclusion",
          "exclude": {
            "types": {
              "server": { "private_key": true, "internal_ip": true },
              "client": { "password_hash": true, "session_token": true }
            }
          }
        }
      }
    }
  }
}
Validation Rules
- Field names must match your data's column names
- Values must be boolean (true to hide, false to show)
- Essential binding fields cannot be excluded
- Cannot mix inclusion and exclusion rules for the same fields
When to Use Exclusion vs Inclusion
- Use exclusion when you want to show most fields but hide a few specific ones
- Use inclusion when you want to show only a few specific fields and hide everything else