Data Mapping is now in Connect Frontline. It shows how each field gets from your HR system to the platforms you provision, and flags any required field that isn't mapped before it breaks provisioning.
In this article
Get started
Every account Connect Frontline provisions is built from HR data. That data passes through two mappings: from the HR system(s) into Connect Frontline, then from Connect Frontline into each platform.
If a required field isn't mapped at either step, the record that reaches the platform is incomplete. Provisioning fails quietly, and the problem stays hidden until bad data reaches a downstream platform.
By then, the symptom is in one place and the cause is in another. Someone has to trace a failed account back through the platform, Connect Frontline and the HR system to find a mapping nobody had checked.
In October, we introduced Data Mapping. It shows how fields flow from the HR system into Connect Frontline, and from Connect Frontline on to each platform.
Both mappings are managed in one place, under Data and Integrations in the Admin Console.
Without a warning, an unmapped required field surfaces as a failed account in a downstream platform. With Data Mapping, it surfaces in the mapping itself, before it breaks provisioning.
A typical check looks like this:
1. Connect a new HR source, or change how an existing source's fields are used.
2. Open Data Mapping and check the source's mapping coverage.
3. Look for any required fields flagged as unmapped.
4. Map those fields before records reach a platform.
The coverage count gives a quick read on each source. Anything short of full coverage on required fields is worth checking before the next sync.
Data Mapping is available to all customers now. If you already use Connect Frontline, you'll find it under Data and Integrations in the Admin Console.
New to Connect Frontline? Book a demo to see how it gives IT control over frontline access.
Related: Introducing Unmanaged Accounts