web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Integration Manager - "ADO Field is nothing" Error

(0) ShareShare
ReportReport
Posted on by

All:

I'm attempting to import Vendors for a new implementation and have recieved the following error:

ADO Field is nothing

Microsoft.Dynamics.GP.IntegrationManager.CBOMADO.ADOField.Initialize

I have seen one other post on this forum related to this error, but unfortunately that person did not post the resolution.

Any ideas?

Best,

Todd M Bowlsby

*This post is locked for comments

I have the same question (0)
  • SiTheITGuy Profile Picture
    2 on at
    RE: Integration Manager - "ADO Field is nothing" Error

    This is now a REALLY old thread but still happens. To throw my 2 cents into the mix; I discovered that a user with a new machine had a "," set as a decimal separator in their regional settings that caused the same error. I changed the "," to a "." and the preview worked. So add regional settings to your checklist in future.

  • Community Member Profile Picture
    on at
    RE: Integration Manager - "ADO Field is nothing" Error

    I know this is a very old post by now, but for future troubleshooting, I recently had this problem and was able to resolve it by right-clicking the source, clicking Proprties, and from within the Properties window browsing out to locate my source file manually. For some reason this worked, when nothing else had. Perhaps it will do the same for whomever may read this.

  • Mariano Gomez Profile Picture
    26,225 on at
    Re: Integration Manager - "ADO Field is nothing" Error

    I believe this error tends to be environment specific, hence proposed resolutions may or may not work. This problem is generally related to file names, column names, and even data within the file. However, it could also be related to the IM components themselves. It's almost a trial and error situation.

  • Mathieu Rivest Profile Picture
    30 on at
    Re: Integration Manager - "ADO Field is nothing" Error

    we had a problem this morning, found this thread and none of the solutions worked. But I found out the problem was the filename. We can't have a space in the file name.

  • Suggested answer
    Community Member Profile Picture
    on at
    Re: Integration Manager - "ADO Field is nothing" Error

    The GP support team just released a new blog around this topic. Hopefully this information will be able to help resolve this question. community.dynamics.com/.../ado-field-is-nothing-error-message-in-integration-manager.aspx

  • Community Member Profile Picture
    on at
    Re: Integration Manager - "ADO Field is nothing" Error

    Is the source file definately closed? If its not, you wll get this error.

    If so, close out of GP altogether and go back in and try again.

  • Community Member Profile Picture
    on at
    Re: Integration Manager - "ADO Field is nothing" Error

    FYI - i had the exactl same issue today and none of the resolutions seemed to work. This was a AP Voucher integration which was working fine as of yesterday. Tried to preview the query (Advanced ODBC reading from .csv file) today, and boom - ADO error!

    Finally, i deleted the schemas.ini file in the source file folder and re-tried, and it worked.

    Thanks,

    Sandeep.

  • Suggested answer
    Community Member Profile Picture
    on at
    Re: Integration Manager - "ADO Field is nothing" Error

    What bill is saying is true, sometimes when you save data from excel to csv, tab etc, it will export used columns/rows, it might be adding additional columns or additional rows at the end of the saved file.

    One rule of thumb I use when saving text files from excel is I find the last column I used and delete the rest, find the last row and delete the remaining, so when I export the file it saves only data and no extras.

    Please verify

  • Suggested answer
    Bill Campbell Profile Picture
    12 on at
    Re: Integration Manager - "ADO Field is nothing" Error

    When I was looking for help on this same error message I read over the different suggestions, all of which I was also able to confirm were / are correct.  The suggestion on the column header made me go look at the column headers I used.  

    I had read the original data from the RM00102 table into excel - made the changes to the data I wanted, in this case creating a new Address ID with a different name - and then using the exact format, saved the file as Tab and started the import.

    Here is what I finally figured out.  When I looked at the Column Names in the IM Properties, I found that (1) at the end of my data, there were a number of BLANK Headed Columns (2) DEX_ROW_ID was still showing.

    Edited the original file, removed the extra columns from the end of the table, including DEX_ROW_ID and resaved - in Integration Manager - refreshed the Column Headers - and sucessfully ran the Integration of 50,000 items with no errors.

    Thanks to the suggestions found on this post I was able to get this done and resolved in under an hour.

    Thanks everyone.

  • Dave Bosserman Profile Picture
    980 on at
    Re: Integration Manager - "ADO Field is nothing" Error

    Check your column headers for 'reserved' words.  Some of the common reserved words that will cause this error are Date, References, Number... there's a whole list of them in this kb:

     http://support.microsoft.com/kb/321266

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans