Generic SQL Error When Migrating Data To Dynamics 365
Article ID: KB0077185
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud Integration - Connect ( Scribe ) | - |
Description
Product: Scribe Online/Insight
Connector/Adapter: Microsoft Dynamics 365/CRM
The generic SQL error is just that "a generic message", which is passed back to Scribe from the API when the error occurs. The main reason for this error is that there is some data constraint on the target that is being violated by the data inserted, so its most likely a data issue with one or more mapped fields.
Connector/Adapter: Microsoft Dynamics 365/CRM
The generic SQL error is just that "a generic message", which is passed back to Scribe from the API when the error occurs. The main reason for this error is that there is some data constraint on the target that is being violated by the data inserted, so its most likely a data issue with one or more mapped fields.
Issue/Introduction
The generic SQL error is just that "a generic message", which is passed back to Scribe from the API when the error occurs. The main reason for this error is that there is some data constraint on the target that is being violated by the data inserted, so its most likely a data issue with one or more mapped fields.
Resolution
Troubleshooting Steps:
1. Remove the mapped fields a few at a time, leaving only the required fields and run the job.
2. Continue this process until you receive the error message again. This will identify which mapped field is causing the issue.
3. Once you identify the problem field, create a record via the UI for CRM inserting the value from the source record. This will typically tell you what the problem is.
In some other cases, it could be plugin(s) or business rules in Dynamics 365 causing the issue, so the customer would need to have their CRM admin get and review the CRM trace logs.
1. Remove the mapped fields a few at a time, leaving only the required fields and run the job.
2. Continue this process until you receive the error message again. This will identify which mapped field is causing the issue.
3. Once you identify the problem field, create a record via the UI for CRM inserting the value from the source record. This will typically tell you what the problem is.
In some other cases, it could be plugin(s) or business rules in Dynamics 365 causing the issue, so the customer would need to have their CRM admin get and review the CRM trace logs.
Feedback
Yes
No
Powered by
