“ADO field is Nothing” by Integration Manager

By in Dynamics GP, System on Thursday, September 9th, 2010

If you have come across the “ADO field is nothing,” error by Integration Manager, don’t worry you are not alone.  Many have received this error and have lived to tell about it.  Others will soon receive it…if they forget to install the latest Integration Manager SP after they’ve installed their latest Dynamics GP service packs. 

A few reasons “why?” you may receive this error….

1.   You have your data file (a.k.a. the source file) open.    Check for this, see if excel or a text file is open.  If you have the file open…just close the file.  This failure to import is because integration manager (IM) cannot read the file.  IM thinks the file is still being written to and will fail to import.  

2.  Check your column headers for special characters or words known as “Reserved Words.”  The idea is similar to Reserved Parking.  IM has set aside certain words and special charcters for its own uses in IM coding.  Using any of these Reserved Words results in you getting booted or the integration fails to run.  For a complete list of Reserved Words CLICK HERE.

3.  If you have installed the latest Service Pack for Dynamics GP and fail to do so for Integration Manager you’ll run into this error.  Service Packs must match Dynamics GP Service Packs across the board not just for IM but for all the other applications in relations with Dynamics.

Hopefully, this information will help you to avoid some of the, “Tales of the ADO Nothing” by IM.

5 Responses to ““ADO field is Nothing” by Integration Manager”

  1. [...] now at DynamicsCare, Amy Walsh has a great look at the “ADO field is Nothing”  error that shows up in Integration Manager when it can’t find the source data. Published: Friday, September 10, 2010, 02:00 [...]

  2. Pooja says:

    Hey, I checked all the 3 steps.
    I am trying to open from SQL so I made sure that SQL was closed. I also checked for the reserved words. And I don’t have service pack for GP< so I don't think I have to install service pack for Integration Manager. I am still getting the same error 'ADO Field is nothing' while clicking on Preview on the SOURCE. Any help will be appreciated.

  3. Jessica says:

    I found another reason that this message may happen. If you’re integrating a text file, make sure there are not additional periods in the name before the .txt extension.

  4. Sandy D'anna says:

    I’m the GP Sys Admin for my company, We rarely see the above error but here it came today and my user had the Excel file opened. Textbook solution. Thanks

Leave a Reply

*
*