When multiple geometry layers (polygons, lines, or points) are present within nested repeatables, all geometries currently inherit the color of the parent record’s status. This causes overlapping polygons at different hierarchy levels to appear visually indistinguishable (“blue on blue on blue”). Users need a way to differentiate these layers through distinct colors or other visual cues. Example Use Case: In one customer's operational workflow, a Location record represents a broad operational area (e.g., a neighborhood or zone). Each Location includes a repeatable for Work Orders, which may each define a smaller polygon area within that Location (e.g., individual assessment zones). Within each Work Order, a nested Daily Work Update repeatable contains additional geometries drawn by field teams to document daily progress (e.g., polygons or lines showing the work actually completed). When viewed on the map, all three of these layers are displayed using the same color derived from the parent’s status. This results in a single, indistinct mass of overlapping shapes, making it impossible to visually distinguish which geometry belongs to which level of the hierarchy.