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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

PO Approval Workflow

(0) ShareShare
ReportReport
Posted on by 122

Hello,

Am facing a problem with Purchase Order approval workflow in NAV 2017. 

Approval setup is configured in such a way there are two approving authorities in the hierarchy. The first approver has a limit of approving PO upto $1000 and anything above shall go to the second approver. Everything is working fine except when the second approver "Rejects" the approval for any PO and the status of the PO instead of reopening remain in Pending Approval stage. This is causing trouble as the Purchasing Agents are not able to edit the document and resend it for Approval again. 

When the first approver rejects the PO status changes to Open but if at the second approval stage if the record is rejected the status remain Pending Approval only. Can anybody shed light on what might be the cause here?

Thanks,

Krish

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    RobertasR Profile Picture
    5,004 on at

    Hi Krish,

    It isn't standard NAV behavior - I have used approval workflows many times and it works fine. It might be a setup issue or add-on / development that breaks the logic.

    To check the setup, make sure that there is only one line for Workflow Event 'Request is rejected' and it doesn't have Conditions. Also make sure that the response includes 'ReOpen the Document'.

    Also, see what is happening with approval entries when the document is Rejected. Are they all set to status Rejected, or some leave with Open? If they are all rejected, the workaround would be to manually ReOpen the document (theoretically this might be allowed) for editing after PO stays in Pending Approval status.

    Hope that helps

    Robertas

  • Krish-NAV Profile Picture
    122 on at

    Thank you Mr. Robertas.

    Honestly we couldn't identify the exact reason. Most likely reason we have come to believe is modifying the workflows by another during operations. Rejecting a PO by first level approver sets the status to "Open" but not by the second approver. As you said there is only one line for When Approval Request is Rejected and condition is Always. Response includes Reopen the document as second step.

    Also, adding additional responses like creating notifications impedes the process so we removed the step.

    We disabled the existing workflow after asking all users to close NAV, created new workflow from scratch, enabled it and restarted the NAV service. All seems to be working fine now.

    Regards,

    Krish

  • Krish-NAV Profile Picture
    122 on at

    Approval entries are fine. Wherever the PO is rejected it creates appropriate entry stating Rejected by which approver. No issues there. As you said it seems like somewhere in the code the logic breaks down. As am not a technical guy grappling with the issue here. I come to believe that in the beginning some of the modifications to Responses might be causing this issue.

    Anyway, creating the workflow from scratch has resolved the issue but personally it is nagging not knowing the exact root cause.

    Regards,

    Krish

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

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…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans