What a path means#
A path names a field in a Data Table row. Use a dot between nested structs and their fields, such as Stats.Power or Info.Rarity.
Every part before the final field must be a struct. A path cannot continue through a number or text field.
Discover valid paths#
- Connect the table to Get Leaf Property Paths.
- Choose the field you need from the returned list.
- Pass it to Get Property Type At Path.
- Select a filter or read node matching that type.
This is also useful after renaming a row-struct field.
Match the field type#
An integer field needs an integer node; a decimal field needs the float variant. Enum fields are compared by numeric value. Get Enum Entries At Path lists the entry names in order; for a Blueprint enum, an entry's position, starting at 0, is its value.
Know the limits#
Paths support nested structs, but not array elements, map entries, sets, or fields reached through object references. Use your own Blueprint logic for those cases.
If a path is absent from the supported path list, inspect the row struct and check whether the final value type is supported. Components of engine value types, such as Location.Z, also work as paths even though the list shows only Location.
Fix a path error#
Use the exact name returned by the inspect nodes. Check spelling, nesting, and the selected table. Stats.Power.Extra is invalid when Power is already the final numeric field.