Fixes
- A Sync assigned a Transform Map Group collected data as if it had no group, always using the default (ungrouped) Transform Maps. The rest of the ingestion correctly used the group's maps, so the effects were indirect:
- A field added only to a group's Transform Map rendered empty. Its source column was never requested from IP Fabric, so the value arrived absent — the group's map was applied, but had no data to read. Adding the same field to the default map worked around this.
- An endpoint whose only Transform Map belonged to a group aborted the sync with
No transform map found for endpoint, despite the map existing.
- A field added only to a group's Transform Map rendered empty. Its source column was never requested from IP Fabric, so the value arrived absent — the group's map was applied, but had no data to read. Adding the same field to the default map worked around this.
- The Sync edit form built its per-model checkboxes from the default (ungrouped) Transform Maps only. A group mapping a NetBox model that no default map covers got no checkbox, so that model could never be enabled and was skipped without explanation. The checkboxes now follow the selected groups.
[!caution] Changing Transform Map Groups does not redraw the form
The per-model checkboxes are rebuilt when the form loads. After adding a group that targets a new NetBox model, save the Sync and reopen it to see — and enable — that model.