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

Notifications

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) / Action is required whe...
Microsoft Dynamics GP (Archived)

Action is required when condition is met not working Requisition Workflow GP 2016

(0) ShareShare
ReportReport
Posted on by Community Member

I have a Requisition Approval workflow setup similar to other companies I have setup and are working smoothly. The problem with this company is that the workflow I'm testing uses only one step, assigned to me, whenever I use: "action is required only when the following condition is met", the workflow history shows that the step didn't needed no action which is wrong. No matter if I use amount, line cost, comments, it just doesn't work. It has a manager assigned to the workflow. Also project is configured, no po enhancements activated. Like I said first time it happen. The workflow only functions with steps that has the "always requires action" marked. It sends emails notifications and approvals can be completed for this type of step.

*This post is locked for comments

I have the same question (0)
  • Tim W Profile Picture
    Tim W 2,925 on at

    Do you have the 'Allow Originator to be an Approver' checked?

  • Community Member Profile Picture
    Community Member on at

    Thanks for the reply, Tim. Yes, I have the Originator as an approver marked. Like I mentioned before everything works fine if the step is configured as "always requiring action", I can approved it and receive the notifications also. The problem is when I create a step with some type of condition. Any condition, unit cost, document amount, extd cost, comment ID, it says: "No action requiered".

  • Tim W Profile Picture
    Tim W 2,925 on at

    We have Workflow 2.0 running for PO's and AP Approvals.  For AP, each approver is a conditional step.  We base that off of Transaction Description matching the Step Name (Step name being the name of the approver).  We have about 90 steps, all conditional and it works for us (not elegant, but works).

    For PO, we nest conditional steps on PO Subtotal field.

    Sample:  where PM Transaction Work.Transaction Description is '<approver name>'

    Is it possible you're testing on a field without value or the condition itself is not proper?  All I can think of.  If you want to PM me a screenshot I'd take a look.  I realize 'it works for me' is not helpful but it does work for me.

    Tim

  • Community Member Profile Picture
    Community Member on at

    Hi Javo,

    Did you ever find a solution / cause for this issue?

    Thanks,

    Ian.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Hello Ian,

    Turns out the work around was to assigned the gl account to the line item and everything worked after that. Strange, because I don't have to this with any other workflow in any other client. This solved the problem in this particular case.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans