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 :
Microsoft Dynamics GP (Archived)

Running IM on a development server

(0) ShareShare
ReportReport
Posted on by

We've created a development GP 2013 server.  We have custom IM tables that are used for integration.  Whenever we run the Integration we get the following error.

 

DOC 2 ERROR: Field 'Document Number' does not have a default value. - Destination Field

ID: Document Number - Field Value: T-8006-02

DOC 2 ERROR: Field 'Distributions.Distribution Account' does not have a default value. -

Destination Field ID: Distributions.Distribution Account - Field Value:

It states the batch does not exist but the batch was created and it's status is "Avaliable".

*This post is locked for comments

I have the same question (0)
  • Frank Hamelly | MVP, MCP, CSA Profile Picture
    46,625 Moderator on at

    What kind of integration is this?  POP?  Payables? SOP?

  • JJdynamics Profile Picture
    25 on at

    Hi Frank,

    This is Payables Transaction. I work with AnettaJ. We both are working on this issue.

    Thanks

    Justin

  • Suggested answer
    Frank Hamelly | MVP, MCP, CSA Profile Picture
    46,625 Moderator on at

    The error messages indicate that your mapping has 'Default' set as the source for Document Number and Distribution Account but there are no defaults set in GP for those values.  Should those values not be coming from your source file?

  • JJdynamics Profile Picture
    25 on at

    Hi Frank,

    Thanks for your reply.  No they are not set as default. I have set it to take from the Use source field. That is what I have set in the mapping section.

    thanks

    Justin

  • Frank Hamelly | MVP, MCP, CSA Profile Picture
    46,625 Moderator on at

    Okay, next question - what is the nature of the 'custom tables' referred to in the first post?

  • JJdynamics Profile Picture
    25 on at

    The Custom tables actually refer to the source Text files. These are comma delimited files.

  • Suggested answer
    Bill Campbell Profile Picture
    12 on at

    Frank has you looking at the source table - question would be 'are there values that are real account number or index values in that table?

  • Suggested answer
    Frank Hamelly | MVP, MCP, CSA Profile Picture
    46,625 Moderator on at

    It's really challenging to troubleshoot an issue like this online because of the number of variables associated with an integration but I would be looking at the integrity of the source file.  Check to make sure that no blank rows or fields exist.  Let us know what you find.

  • JJdynamics Profile Picture
    25 on at

    Yes the source file does have a GL account number as one of the fields. But the error does not indicate to that field. I don't know if that helps.

  • JJdynamics Profile Picture
    25 on at

    There are no blank rows  or fields. It is a 2 row file. I am testing with a sample file.

    Also, I am curios about one thing. The integration manager was installed with configuration from a production server. I moved the access DB file to the local DEV server and recreated a new integration with the source and the destination. Is it possible that even though I created a new integration the mapping might still be pointing to the other server? Is there a way to find out from IM which GP server it is pointing to?

    thanks,

    Justin

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!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans