Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


Symptoms

In Integration Manager for Microsoft Dynamics GP, when you use a Microsoft SQL Server table as an Integration source, the transaction line information is not imported, or it is only imported for some transactions.

↑ Back to the top


Cause

This issue occurs because the Datatype setting of a date column is set to Date. This setting should be set to String.

↑ Back to the top


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:
  1. Right-click the Integration source that you are using, and then click Preview.
  2. 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.
  3. For the Advanced ODBC source, follow these steps:
    1. Open the Source Properties window, and then click the Columns tab.
    2. Change the Datatype setting for the Date columns from Date to String.
    3. Make this change on all integration source files that have a date column that uses a date as the data type.
  4. If you are using a Simple ODBC source, change to an Advanced ODBC source, and then perform steps 3a to 3c.

↑ Back to the top


Keywords: kbnosurvey, kbexpertiseadvanced, kbmbspartner, kbexpertisebeginner, kbtshoot, kbmbsmigrate, kbprb, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 970225
Revision : 1
Created on : 3/3/2017
Published on : 1/6/2015
Exists online : False
Views : 66