Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

Document Attach for AP Transactions while using Transaction Workflow

Posted on by

We have a customer who is using Payables Transaction Workflow and are on GP2016 R2.

They want to attach the scanned invoice to the payables transaction and have that sent along with the email generated when a transaction is submitted.   You have to attach the document in the transaction entry window Ribbon in order for it to be emailed.   The problem we found is that once the transaction has been approved and then posted the attached document is gone.  We do not see it when we inquire on the transaction.   We found if you attach the document at the note level of the voucher it will stay with the document when it is posted, however it does not get sent in the email to the user who needs to approve the transaction.   It appears that you have to attach it in both places which is not a good solution.  Also we found that once you activate the AP Transaction workflow, even if you inactivate the workflow the document attach in the AP Transaction Ribbon does not stay with the transaction after posting.   Prior to turning on the AP Transaction workflow the document attachment in the AP Transaction Entry window worked fine.

Has anyone else had this issue?   It appears to be a bug.   I tested it in GP2015 R2, GP2016 and GP2016 R2.

Thanks

Ray 

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Document Attach for AP Transactions while using Transaction Workflow

    You most likely have the 'delete' document still checked.  Uncheck it in the document attach set up. - cheers

  • WrqnHrdr Profile Picture
    WrqnHrdr on at
    RE: Document Attach for AP Transactions while using Transaction Workflow

    I am on GP2015R2 and have just started using AP workflows.  I am finding that you must attach files from the ribbon to be able to send in emails.  The problem I just encountered was that the DOCNUMBR in the CO00102 table is NOT the DOCNUMBR from the tramsaction, further I am seeing the wrong VENDORID listed in the same table.  Has anyone else seen this behavior?

  • Ray Nist Profile Picture
    Ray Nist on at
    RE: Document Attach for AP Transactions while using Transaction Workflow

    Hi Mick - thanks for the update!

  • Suggested answer
    Mick Egan Profile Picture
    Mick Egan 3,557 on at
    RE: Document Attach for AP Transactions while using Transaction Workflow

    Ray,

    Interestingly this issue appears on GP2016R2, as I initialliy raised the issue against GP2015, see "Document Attachment - Not moving to History", and no comments were forth coming.

    We manually update the Document Attach Tables with the History values and the documents then appear on the PM Enquiry screen.

    Looking at creating a Store Procedure to run as a job and update any records not attached to history to run on a regular basis as a work around.

    Mick

  • Tim W Profile Picture
    Tim W 2,925 on at
    RE: Document Attach for AP Transactions while using Transaction Workflow

    Hi Ray,

    I'm in the mist of evaluating these features and had concerns initially when I came across your post. I was looking for thoughts on another blocking issue we have with all this.  What I'm finding is I still do still see the attachment on posted documents but I can only access them from the ribbon Note ID and not the window note ID.

    At first I was alarmed with this but doing some testing now I've come to appreciate this feature.  Again, I can inquire on a posted document using the ribbon note and can access what was sent with the approval e-mail.  If you can't that is a problem I don't have (2015 R2).  The AP document has two different note attachment id's and the one that is the ribbon note does not allow any further attachment or adding/deleting of notes unlike the note in in the window.

    This makes sense from an audit standpoint and actually is a nice feature.  Attachments on the document which can be edited / updated / deleted per standard GP function are segregated from the attachments from the approval workflow which are locked in read only mode after approval.

    General comment, one thing missing for any long time GP person seems to be the lack of detailed documentation on best practice use on the features, hitting F1 from any window just isn't what it used to be.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans