Transaction line information is not imported when you use a Microsoft SQL Server table as an Integration source in Integration Manager for Microsoft Dynamics GP
This article provides a resolution for the issue that the transaction line information isn't imported when you use a Microsoft SQL Server table as an Integration source in Integration Manager for Microsoft Dynamics GP.
Applies to: Microsoft Dynamics GP
Original KB number: 970225
Symptoms
In Integration Manager for Microsoft Dynamics GP, when you use a Microsoft SQL Server table as an Integration source, the transaction line information isn't imported, or it's only imported for some transactions.
Cause
This issue occurs because the Datatype setting of a date column is set to Date. This setting should be set to String.
Resolution
To resolve this issue, first verify that the Options tab is set to Use Source Recordset in the Destination Mapping window. If the line information is still not imported, follow these steps:
Right-click the Integration source that you are using, and then select Preview.
If the Datatype setting of a date column displays a date and time stamp, for example, 01/01/2009 12:00 AM, change the Datatype setting of the column to a String data type.
For the Advanced ODBC source, follow these steps:
- Open the Source Properties window, and then select the Columns tab.
- Change the Datatype setting for the Date columns from Date to String.
- Make this change on all integration source files that have a date column that uses a date as the data type.
- If you are using a Simple ODBC source, change to an Advanced ODBC source, and then perform steps 3a to 3c.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for