To access Field Mapping, go to Integrations → Dynamics → Configure → Step 2: Field Mapping.
Important: Dynamics 365 requires field types to match exactly and does not convert values automatically. Any type mismatch will cause the export to fail.
Understanding the Status Icons
Icon | Status | What it means |
✓ Blue | Compatible | The field types match. No action needed. |
! Yellow | Warning | The field types may be incompatible. Dynamics does not auto-convert types — review this mapping carefully before saving. |
✕ Red | Error | The mapping cannot be applied. The export will fail for any record using this mapping. |
Warning: Do not save a configuration with red icons. Exports will fail for all records using that field mapping.
Which Dynamics Field Type Should I Use?
Use this table as a reference when selecting the destination Dynamics field for each Enginy field.
Enginy field | Recommended Dynamics field type | Notes |
First name, Last name, Job title, Email, Phone | Text / TextArea | Standard text fields. Fully compatible. |
Number of employees, Years in role, Growth % | Integer / Decimal / Floating Point | Map to a Dynamics numeric field. |
Created at, Last activity at CRM | DateTime (timezone-aware) | Never map to a Text field — Dynamics will reject it with a typeMismatch error. |
Outreach Stage, Sequence Status | Choice (single) | Value must match an existing option exactly. |
Languages, Sub-industries | Choice (multi) | Values must match existing options exactly. |
LinkedIn URL, Domain, Website | Text | Map to a standard text field in Dynamics. |
Personal emails, Other phones | Text | Use Professional email and Mobile phone instead where possible to avoid sending arrays. |
Boolean fields (e.g. verified) | Two-Option (Boolean) | Map to a Dynamics Two-Option field. |
Status / State fields | Status / State (numeric codes) | These fields only accept numeric codes, not text labels. |
Yellow Warning: What to Do
Dynamics 365 does not convert field types automatically. A yellow warning means the mapping is likely to fail and must be reviewed before saving.
1.Text mapped to a Choice (dropdown) field
If you map an Enginy text field to a Dynamics Choice field, Dynamics will reject the value if it does not match one of the configured options exactly. Dynamics returns a typeMismatch error in this case.
How to fix it:
Create an AI Variable with output type One off and define the tag options to exactly match the Dynamics Choice field options.
For Fixed Value or Engagement fields: enter the exact option value directly in the field mapping configuration.
For Manual Export fields: enter the exact option value at the time of export.
2.Date field mapped to a Text field
Enginy stores date fields (such as Created at or Last activity at CRM) as full date-time values. Dynamics will reject these values if the destination field is a plain text field, returning a typeMismatch error.
How to fix it: Map Enginy date fields to a Dynamics DateTime (timezone-aware) field.
3. Status and State fields
Dynamics Status and State fields only accept numeric codes, not text labels. Sending a text value will cause the export to fail.
How to fix it: Use the numeric code that corresponds to the status option in your Dynamics configuration.
Red Error: What to Do
A red icon means the mapping will always fail. There are two reasons this happens:
1.Field does not exist in Dynamics
The destination field you selected no longer exists in Dynamics. This typically happens when a field has been deleted or renamed after the mapping was configured.
Dynamics returns: "The field 'X' does not exist on the 'Y' entity. Please check your Sync Settings."
How to fix it: Remove the mapping and select the correct current field in Dynamics.
2.Read-only Dynamics field
The destination field in Dynamics is read-only and cannot be updated by Enginy. This typically affects system-generated fields.
How to fix it: Remove the mapping and choose a writable Dynamics field, or contact your Dynamics administrator to confirm field permissions.
Common Dynamics Mapping Mistakes
Mistake | What happens | How to fix it |
Mapping a Company field in the Contacts tab (or vice versa) | Export fails with a field mapping error | Verify that only Contact fields appear under Contacts, and only Company fields under Companies |
Mapping an Enginy date field to a Dynamics Text field | Dynamics returns a typeMismatch error | Map to a Dynamics DateTime (timezone-aware) field instead |
Mapping an Enginy text field to a Dynamics Choice field without matching option values | Dynamics returns a typeMismatch error | Use an AI Variable (One off) with the exact option values |
Mapping to a Dynamics Status or State field using text | Export fails — these fields only accept numeric codes | Use the numeric code for the corresponding status option |
Mapping to a field that no longer exists in Dynamics | Dynamics returns an invalid field error | Remove the mapping and select the correct current field |
Mapping to a read-only or system field | Export fails | Choose a writable field instead |
Updates failing for specific contacts | Connection or record issue | Try re-exporting them to create updated records in Dynamics |
Saving mappings with red icons | All records using that mapping fail to export | Fix or remove any red-icon mappings before saving |
Need More Help?
If you have reviewed your mapping configuration and the export still fails, contact our support team with:
The name of the Enginy field and the Dynamics field you are trying to map
The error message or icon you are seeing
A screenshot of the Field Mapping configuration if possible