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

Notifications

Announcements

Season of Giving Solutions is Here!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Integration Manager Er...
Microsoft Dynamics GP (Archived)

Integration Manager Error - Query Not Found in Database ADO Field is Nothing

(0) ShareShare
ReportReport
Posted on by Community Member

I am having an issue w/ an integration. I am doing a General Journal integration. I am using GP 2013 and Integration Manager all of the correct Service Packs.

The issue comes up with a field I am trying to import into the Note field. If I set the Datatype for the field in the tab-delimited text file to String, the integration works fine. However, I would like to set the Datatype to Long VarChar b/c I have information that is longer than 255 characters that I want to put in the Note field. When I switch the datatype for the field to Long VarChar in both my header file and my line file and attempt to run the integration, I receive an error that says:

"ERROR: Unable to open source queries because Query 'Expensify Header' is not found in the database. - Unable to open source queries because Query 'Expensify Line' is not found in the database.
ADO Field is nothing.
Unable to open source queries because Query 'Expensify Header' is not found in the database. - Unable to open source queries because Query 'Expensify Line' is not found in the database.
Unable to open source queries because Query 'Expensify Line' is not found in the database."

I have verified that I have not special characters in column names. In addition, I have verified that I am not using any columns named w/ reserved words. As I stated, the Integration work is fine if the datatype is String, but fails when I switch the Header and Line to Long VarChar.

Any thoughts on what I am doing wrong?

*This post is locked for comments

I have the same question (0)
  • MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    When I look at the Note field properties in Integration Manager, it states the data type is String and that it supports 32768 characters. This is the actual IM datatype, so there's no need to change the mapping type to Long VarChar and you shouldn't experience any truncation.

  • Community Member Profile Picture
    Community Member on at

    Thanks. I appreciate the reply. However, the String is truncated at 255 characters. According to the Integration Manager manual I believe that the String datatype in the Integration always truncates to 255 characters regardless of the allowed field length in the target. That is why I was trying to use Long VarChar since the documentation directed that was what to use in these cases.

  • MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    I saw the help file where it states that, so that leaves us with a couple alternatives:

    1. The Note field data type is incompatible with the IM Long VarChar data type, in which case you would have to open a support case to have Microsoft confirm.

    2. The length of all the fields including the note exceeds IM's capacity, although the help file references to use a Long VarChar if that happens to be the case, but there's a chance that's broken too, which takes us back to opening a support case with Microsoft to confirm.

    3. Does your note contain tab characters? This may lead IM to also throw an ADO error. These are harder to spot, but run the test I suggest below.

    Try testing with only one record in the file with, 300 characters in the note - you can make up the note line manually. Then start incrementing the size of the note, perhaps 50 characters at a time to see if you reach a limit of some sorts. If you seem to progress normally, try introducing a tab somewhere in that note and see if you can repro the ADO error.

  • Community Member Profile Picture
    Community Member on at

    I can confirm that there are no Tab characters in the field b/c a scrubbed as special characters, spaces, leading and trailing spaces. I can confirm that with the data type set to String it truncates it at exactly 255 characters.

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

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

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

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans