See every submitted form field in your Concierge logs, mapped or not.
What's Changed and Why
Previously, any field not mapped in a router's Trigger was dropped before it reached the log. You could see the mapped fields, but if a field wasn't capturing data, the only way to find out why was to open the page source and compare it by hand.
What's Possible
- See every field in the form payload, mapped and unmapped, in one place
- Unmapped fields sit in a collapsible "Unmapped Form Fields" group below the mapped rows, with a count badge (collapsed by default)
- Each unmapped row carries an Unmapped badge, with the field name, captured data, and data source still populated
- Expand the group and use the "Go to Form Mapping" link to jump straight to the router's Trigger and map the field
- Works the same on both the form-in-progress/abandoned log and the post-submission log
Things to Note
- Applies to logging only - a field showing in the log doesn't mean it's captured; Routing Rules and the Create/Update Record node still require it to be mapped
- No backfill, historical logs render as they always did
- Third-party Form trigger only
- Config params (id, assignee, accountId) and smart param slugs are stripped out so they don't add noise
Where to find it
- Concierge logs, on both the form-in-progress/abandoned view and the post-submission view.