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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / GP 2016 Integration Ma...
Microsoft Dynamics GP (Archived)

GP 2016 Integration Manager Before Query Error

(0) ShareShare
ReportReport
Posted on by Richard Wheeler 75,852 Moderator

I am trying to create a PO integration routine using Integration Manager. I am getting this error which makes absolutely no sense. There is no Before Query script

on the PO Header and I see no special characters in the csv file. Does anyone have any clue as to what may be causing this? eConnect is installed as well as the eConnect components for IM.

The source could not be initialized due to the following problem:
 - Error Compiling Script 'Before Query .TWO PO Header' Line -5:
Invalid character

*This post is locked for comments

I have the same question (0)
  • Derek Albaugh Profile Picture
    Derek Albaugh Microsoft Employee on at

    In Integration Manager, if you right-click on the integration name and go into Properties, under the 'Scripts' tab, is there any scripts listed there?

    It appears the script may be named 'TWO PO Header'.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,852 Moderator on at

    That is the odd thing. There are no scripts anywhere in this integration. Perhaps I should start a new one. It may be corrupt.

  • Derek Albaugh Profile Picture
    Derek Albaugh Microsoft Employee on at

    That is odd, maybe that specific integration got corrupted in some way.

    I'd try building a new one with the same settings to test, see if that resolves the message.

    Thanks

  • Suggested answer
    Sheilajr Profile Picture
    Sheilajr 745 on at

    I feel the need to reply to this conversation even though it was started long ago.  I ran in to this issue just recently on GP 2018 and it was driving me crazy because I started with a brand new integration for a simple GL Account import and there were absolutely no scripts added.  Pure and simple source file with 5 columns.  

    I thought that it might be '/' in the account description or other formatting, but I would still get the error.

    I finally had an "aha" moment and realized that I named my source query with a period in the beginning so that it would show at the top of the source list.  This was the problem.  Once I renamed this text source as _ACCOUNTS instead of .ACCOUNTS the integration ran without errors.

    Lessons learned every day!  Hope this helps someone.

    Sheila

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans