Field reference

43 fields, numbered so the Fields list sorts into the same order as the field wells. 8 are required; the rest add capability as you need it. This page is generated directly from the visual's own field definitions, so the numbers and names here always match what you see in the format pane.

Required — nothing renders without these

#	Field	Purpose
01	Data type	Which entity this row is: NODE, EDGE, GROUP, MEMBER, ASSIGNMENT, STYLE, CHART or ROSTER. Required. Named Data type (not Record type) specifically to avoid colliding with the military's own, differently-meaning Record Type field.
02	Id	Primary key of the row's entity.
03	Title	Display name. On a NODE this is the billet title, e.g. "Commanding Officer".
04	Parent id \| group anchor	EDGE: parent node. GROUP: the node this group hangs beneath, or for a PANEL group the node it attaches beside. Required for structure.
05	Child id \| nested group	EDGE/MEMBER: child node. GROUP: the group this one nests inside. Required for structure.
06	Chain	ADMIN, OPERATIONAL, POSITIONAL, FUNCTIONAL or MENTOR. Required on EDGE rows.
07	Kind \| group type	NODE: BILLET/ORG. GROUP: TRIAD, DEPARTMENT, STAFF_CODES and so on. ASSIGNMENT: assignment type. ROSTER: personnel_type - Active Duty, Civilian, SELRES, and so on. Not the same thing as attachment (Local/CAI/IAP/CAO/etc) - that is always computed from the five uic_* fields now, never read from this column.
08	Sort order	Ordering within a parent or group. Required for predictable layout.

Structure

#	Field	Purpose
09	Role \| group layout	NODE: billet role. GROUP: ROW/COLUMN/GRID/FLANK/PANEL_LEFT/PANEL_RIGHT. MEMBER: member role.
10	Billet code \| grid columns	NODE: the code chip. GROUP: column count for a GRID layout. ROSTER: uic_billet - where this person is billeted/manned, one of five UICs that can place them in a unit's Unassigned pool. Any of the five may be a bare code (PHX01) or code\|title (PHX01\|NR SurgeMain Phoenix); matching ignores the title half.
11	UIC \| group UIC	NODE: unit identification code, shown in the inspector and tooltip. GROUP: the group's own UIC (optional - matching for a TRIAD/COMMAND_LEADERSHIP group's Unassigned pool falls back to its CO's own uic when this is blank). ROSTER: uic_local - where this person is locally attached, the primary of the five UICs a roster row is matched to a unit by. Code\|title format (see the Billet code column) applies here too.
12	UIC title \| lead member	Readable name of the unit the UIC identifies, e.g. "NR SurgeMain Phoenix". On a NODE, shown under the title in the inspector. GROUP: reserved instead for the lead/flagship member's node id — the member gets a marker, sorts first in the grid, and every other member's "Reports to" line in the Inspector points to it. See Builder guide, Example 2. ROSTER: uic_active - where this person is actively serving, if different from billet or local attachment. Same code\|title format as uic_billet.
13	Echelon \| group footer	NODE: echelon band. GROUP: that group's own footer layout JSON. ROSTER: uic_temp - temporary or TAD-type assignments; semicolon-separated for more than one (not comma, since a value's optional \|title half may itself contain one). The only UIC field besides uic_other the visual itself ever writes to.
14	Office code	GROUP only: the office/department code (e.g. N1, N4, S3) - a formal organizational identifier distinct from the group's own display Title. ROSTER: uic_other - any other assignment type not covered by the other four; semicolon-separated for more than one. The only UIC field besides uic_temp the visual itself ever writes to.
15	Scope	Echelon hierarchy level - Branch Leadership, SYSCOM, Program/National, Regional, Unit. Bind it to slice the report by level; also shown on the card tooltip.
16	Organization	Branch or suborganization - Navy, Army, Joint, or a command within one. Bind it to slice by organization; it also stops the group picker offering groups from another organization.
17	Effective from	Start of validity for an edge or assignment.
18	Effective to	End of validity for an edge or assignment.
19	Authority \| group alignment	EDGE: label on an overlay connector, e.g. ADCON or TACON. GROUP: alignment of member cards inside the box (CENTER/LEFT/RIGHT/JUSTIFY) - freed up on this row type once uic itself started holding a real UIC.

Appearance

#	Field	Purpose
20	Details (multi)	Free-text card lines. Bind as many columns as you want - each becomes its own line. GROUP rows, first bound column only: four reserved values instead control the group's box and header independently of its free text - `unboxed`/`false` (no box, no header), `headeronly` (header only, no box border), `noheader` (box only, no header), or leave blank/anything else for both. Any other value is still shown as a normal details line.
21	Style key	Which STYLE row colours this node or group.
22	Style JSON	Colour definition on STYLE rows; band definition on CHART rows.
23	Image	Base64 photo for a billet, or emblem for a group header.
24	Legend	Categorises a billet for the legend.
25	Legend sort \| pool visibility	NODE: orders legend entries. GROUP: Unassigned-pool override for a TRIAD/COMMAND_LEADERSHIP group - blank or nonzero shows its pool, "0" hides it. The Format visual master toggle always overrides this.

Functionality

#	Field	Purpose
26	Value 1	A number on NODE rows that groups roll up. Bind the raw column, not a measure: this visual reads one row per record and does its own aggregation, so letting Power BI aggregate would collapse the table.
27	Value 2	A number on NODE rows that groups roll up. Bind the raw column, not a measure: this visual reads one row per record and does its own aggregation, so letting Power BI aggregate would collapse the table.
28	Value 3	A number on NODE rows that groups roll up. Bind the raw column, not a measure: this visual reads one row per record and does its own aggregation, so letting Power BI aggregate would collapse the table.
29	Last verified	Date this row was last confirmed accurate.
30	Verify frequency	Monthly, Quarterly, Semiannually or Annually.
31	Chart updated	When this slice of the chart last changed.
32	Chart version	Version label for this slice.
33	Chart edited by	Who last changed this slice.
34	Chart comments	Free-text note explaining what changed in this slice and why - travels with the changeset for approval.
35	Chart review status	Draft / In review / Approved / Final.
36	Recall \| official email	Recall detail, on ROSTER rows.
37	Recall \| dual persona email	Recall detail, on ROSTER rows.
38	Recall \| secondary email	Recall detail, on ROSTER rows.
39	Recall \| primary phone	Recall detail, on ROSTER rows.
40	Recall \| secondary phone	Recall detail, on ROSTER rows.
41	Footer field 1	Bind ANY column; reference it in a footer or panel cell as PARAM1. Free on every row type, GROUP rows included.
42	Footer field 2	Bind ANY column; reference it as PARAM2.
43	Footer field 3	Bind ANY column; reference it as PARAM3.

Reading the field names

Two symbols show up in the field wells and throughout this page:

| separates a field's two names when it means something different depending on which kind of row it's bound to — Parent id | group anchor is the edge's parent on an EDGE row, but the billet a group hangs beneath on a GROUP row. See Dual-purpose columns below for the full list.
• separates the field's name from its category tag — REQUIRED, STRUCTURE, APPEARANCE or FUNCTIONALITY — which is what groups the sections on this page and sorts the Fields list itself.

Dual-purpose columns

Several columns mean different things depending on the data type. That is deliberate — a GROUP row has no use for a UIC, and a NODE row has no use for a footer layout — and it keeps the field count down. Dual-purpose fields are marked with a | in their name.

Column	On NODE	On GROUP	On ROSTER
Parent id	—	Anchor billet	—
Child id	—	Parent group	—
Kind	BILLET / ORG	Group type	personnel_type (Active Duty, Civilian…)
Role	Billet role	Layout	Source system
Billet code	Code chip	GRID columns	uic_billet
UIC	Unit code	Group's own UIC (optional)	uic_local
UIC title	Inspector subtitle	Lead/flagship member	uic_active
Authority	—	Alignment	—
Echelon	Band	Footer layout	uic_temp (multi-value; semicolon-separated)
Office code	—	Office/dept code	uic_other (multi-value; semicolon-separated)
Legend sort	Legend order	Unassigned-pool visibility	—

No field in this visual is a measure. Every field well takes a grouping column. If Power BI shows Sum of… next to a bound field, set it to Don't summarize — otherwise Power BI aggregates the table, collapsing many rows into few, and the chart loses most of its content.