This article covers common issues that may occur when exporting records from Cognism to Microsoft Dynamics 365 and explains how to resolve them.
Microsoft Dynamics returns these errors to Cognism during the export process. Reviewing the complete error message is the quickest way to identify whether the issue is caused by the integration, field mappings, permissions, or Microsoft Dynamics validation rules.
Before you troubleshoot
Before investigating an export issue, check that:
- The Microsoft Dynamics integration is connected.
- You are signed in to Microsoft Dynamics.
- Your field mappings have been configured.
- Your Update Rules and Syncing Rules have been reviewed.
- You have permission to create and update Leads, Contacts, and Accounts.
- You have the full error message returned during export.
Error 400 when opening the integration or field mappings
Symptoms
You receive an Error 400 referencing the integration or API, or the Microsoft Dynamics field mappings fail to load.
Cause
The connection between Cognism and Microsoft Dynamics has been lost.
Resolution
Reconnect the Microsoft Dynamics integration.
- Go to Settings > Integrations.
- Remove or log out of the existing Microsoft Dynamics connection.
- Sign in again using your Microsoft Dynamics credentials.
- Reopen the integration settings.
If the problem persists after reconnecting, contact Cognism Support.
Validation error: Number is outside the valid range
Symptoms
You receive an error similar to:
The value '50005000' of 'numberofemployees' is outside the valid range.
Cause
The value being exported exceeds the minimum or maximum value configured for the Microsoft Dynamics field.
Resolution
Review the field identified in the error message.
Confirm that:
- The mapped Cognism value is valid.
- The Microsoft Dynamics field accepts the value being exported.
- The field configuration or validation limits in Microsoft Dynamics are appropriate.
If necessary, update the field mapping or modify the Dynamics field configuration before exporting again.
Attribute cannot be NULL
Symptoms
You receive an error similar to:
Attribute 'emailaddress1' cannot be NULL.
Cause
Microsoft Dynamics requires a mandatory field that was not supplied during export.
This commonly occurs when a required field, such as an email address, has no value.
Resolution
Review the required fields configured in Microsoft Dynamics for the record type being created.
Ensure all mandatory fields contain valid data before exporting again.
Literal cannot be converted to the expected type
Symptoms
You receive an error similar to:
Cannot convert the literal 'Chemical Manufacturing' to the expected type 'Edm.Int32'.
Cause
A text value is being exported into a Microsoft Dynamics field that expects a numeric value, most commonly a Picklist field.
This usually occurs when additional picklist value mappings have not been configured.
Resolution
Review the field identified in the error message.
Verify that:
- The Cognism field is mapped to the correct Microsoft Dynamics field.
- Picklist value mappings have been configured correctly.
- The exported values match the available Microsoft Dynamics picklist options.
Update the mapping before attempting the export again.
Cannot create new contact: Duplicate email
Symptoms
The export fails with an error indicating that a Contact cannot be created because the email address already exists.
Cause
Microsoft Dynamics duplicate detection rules are preventing the creation of another Contact with the same email address.
Resolution
Search Microsoft Dynamics for the existing record.
Depending on your organisation's duplicate handling policy, you may need to:
- Update the existing record instead of creating a new one.
- Modify the duplicate detection rules in Microsoft Dynamics.
- Review your Cognism Update Rules.
Contact your Microsoft Dynamics Administrator if duplicate rules need to be changed.
Validation error: Maximum allowed length exceeded
Symptoms
You receive an error similar to:
The length of the 'jobtitle' attribute exceeded the maximum allowed length.
Cause
The value being exported exceeds the maximum character limit configured for the Microsoft Dynamics field.
Resolution
Review the field identified in the error message.
Reduce the length of the exported value or increase the field length within Microsoft Dynamics if appropriate.
After updating the field configuration, retry the export.
Still experiencing issues?
If the issue persists after completing the recommended troubleshooting steps:
- Reconnect the Microsoft Dynamics integration.
- Verify your field mappings.
- Review your Update Rules and Syncing Rules.
- Confirm the Microsoft Dynamics user has the required permissions.
- Capture the complete error message returned by Microsoft Dynamics.
- Contact Cognism Support if you require further assistance.
Providing the exact error message and the record you attempted to export will help speed up troubleshooting.