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 :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Odd issue when importing PO's using eConnect

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

I have a routine that imports PO's via eConnect. It works fine 99% of the time. Every now and then one comes across reporting this error.

9184 Document is currently being edited by another user.

How can this be possible since I am importing a new PO?

Categories:
I have the same question (0)
  • Suggested answer
    Josh Page Profile Picture
    Microsoft Employee on at

    When you are running the integration, are there users in GP?

    It's possible that if EConnect and a user in the PO entry window "grab" the same next PO number at about the same time you could see that error message.

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    The PO number is supplied from an external database to eConnect so that would not be what is causing this.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,061 Moderator on at

    Richard,

    You say "PO Number is supplied from an external database".. what do you mean by this ?

    Are you using any lookup to grab the next PO number or does the numbering differ completely from the setup in GP ?

    If a lookup is used with the eConnect SP's to grab the next number, it could be conflicting with a new PO that is just created by another user as suggested by Josh..

    Otherwise, I'd double check some of the PM table to check if there isn't already the same document number used in the past.

    PS: what tools are used to process the import to eConnect ?

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    The PO numbers come from a database in a linked server. There is no way that a PO can exist in GP and in this other database until they are brought over to GP. All POs start in this external database. In eConnect all import routines are set to update if they already exist in GP so this makes this even stranger.

  • Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,061 Moderator on at

    could you run a SQL trace while running the import process to try figure out what happens right before the error comes up ?

    www.eonesolutions.com/.../

    dynamicsgpland.blogspot.com/.../trace-database-triggers-using-sql.html

    Are you using straight eConnect calls or the MSMQ services ?

    community.dynamics.com/.../using-the-econnect-incoming-and-outgoing-services-with-msmq

  • Richard Wheeler Profile Picture
    75,852 Moderator on at

    This happens totally randomly and the import process does POs in mass. Less than 0.1% of the time this happens. Trying to catch this will be very difficult.

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 > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 758

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 655 Super User 2026 Season 1

#3
CP04-islander Profile Picture

CP04-islander 496

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans