Mapping suggestionsComing soon
Proposed field matches across sources, with confidence and evidence. Not yet available.
Not available yet
Mapping suggestions depend on mappings, which are still in development. Nothing here can be enabled today.
What is planned
When a dataset first appears or its schema changes, Chartizer will compare its fields against
everything already in the catalogue and propose matches — for example CRM Contacts.Email Address
to the logical field email.
Three signals will decide a suggestion:
| Signal | Example |
|---|---|
| Name similarity | billing_email ↔ Email Address |
| Type compatibility | both resolve to text after normalisation |
| Value overlap | sampled values intersect at 94% |
Value overlap is the one that separates a real match from a coincidence. id and id share a name
and a type across two sources and are very often unrelated.
Each suggestion will carry a confidence score and the evidence behind it, and will wait for a person to accept, edit, or reject it — a wrong mapping silently corrupts every join built on it, so none will be applied automatically.
Until then
See Mappings for what to do in the meantime, and AI in Chartizer for the features available today.