Property Data Types
IntermediateProperty Data Types
When you add a property to a Node Type or Relationship Type, you pick a Type that decides what kind of value its instances can hold and how the value is edited.
Select a type in the Model Navigator, open the Property Definitions section in the Properties panel, and click + Add. Each property row has a Name, a Type dropdown, a Req (required) checkbox, an f(x) (formula) checkbox, and a Default.
The nine data types
| Type | Holds | Edited as | Use it for |
|---|---|---|---|
| String | A single line of text | Text field | Names, codes, short labels |
| Number | A numeric value | Number field | Counts, prices, durations |
| Boolean | True or false | Checkbox | Flags like "active", "critical" |
| Date | A calendar date | Date picker | Deadlines, start dates |
| Option | One choice from a fixed list | Dropdown | Status, priority, category |
| Asset | A reference to a file in your model | Asset picker | Attached diagrams, documents, datasets |
| JSON | Structured JSON data | Validated text field | Raw configuration, payloads |
| Rich Text | Formatted (Markdown) text | Multi-line editor | Long notes rendered with headings and lists |
| Dictionary | A set of key-value pairs | Key-value editor | Labels, tags, free-form attributes |
Setting choices for an Option property
When you choose Option, enter the allowed choices in the Default field as a comma-separated list, for example:
Low,Medium,High
Instances of the type then show a dropdown limited to those choices.
Default values
For most types, whatever you type in the Default field is pre-filled on every new instance. You can override it on any individual node or relationship.
Required properties
Tick the Req checkbox to mark a property as required. This signals to your team (and the AI assistant) that the value should always be filled in.
Computed properties (f(x))
Tick the f(x) checkbox to make a property computed. Instead of a fixed value, the Default field becomes a formula that calculates the value automatically — used by the simulation layer to derive values each timestep. A computed property is shown read-only in tables. (See the Rhai scripting help for how to write formulas.)
Good to know
- Property types apply equally to Node Types and Relationship Types.
- A property defined on a type appears on all instances of that type.
- Renaming a property on the type updates it everywhere — the underlying value is kept.
Try it live
Open these working examples in the app and explore them yourself.
- BlogPost Node Type — Metapad KnowledgeThe BlogPost node type from Metapad's own Knowledge model — its property definitions span several data types (text, date, number, an Option dropdown for status, and a Rich Text body).
- Blog Post 'Why Knowledge Graphs?' — Metapad KnowledgeA concrete node of the BlogPost type — the published article 'Why Knowledge Graphs?', with real property values and the auto ID BP-1.