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

Announcements

Check out the Community Spotlight Video Series
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / PO workflow condition
Microsoft Dynamics AX (Archived)

PO workflow condition

(0) ShareShare
ReportReport
Posted on by Muhammad Fahad 470

Dear Community,

Good day to all of you.

I am using AX 2012 R3 CU10.

In PO workflow, I have few conditions in which I want workflow should not be enabled like;

1. If PO amount is needed to change due to any reason after PO approval, and PO amount is reduced e.g previous PO value was 5000 US$ and new PO value is 4900 US$, then it should not go again for workflow approval. Because amount is downward, so approval is not required. If amount is upward, then approval is required.

2. If user wants to change delivery address on PO header after PO approval, it should not go again for PO approval.

Is it possible?

Regards,

Muhammad Fahad.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    fatihgork Profile Picture
    fatihgork 3,817 on at

    Hi Muhammad,

    I'm not sure for the #1 issue.

    But for #2, in standard functionality you can set it to be approved by application if certain fields are changed since approval. You can check this thread here: Changes to the document are only allowed in state Draft, because change management is activated   and my post at the end of this thread is about that functionality.

  • Sohaib Cheema Profile Picture
    Sohaib Cheema 49,668 Super User 2026 Season 2 on at

    You can always use Workflow document calculated fields for any customized requirement, which are flexible enough to achieve almost anything.

    Already PO workflow document class, has got some methods for PO total value, you can ask your developer to add method for address also. At the same time you need to keep log of data somewhere; based on log table developer will write calculated fields. These logs can be maintained in any customized tables, which will have information such as whether address was changed or yet its same as it was at time of previous submission/version.

  • Community Member Profile Picture
    Community Member on at

    Hey Muhammad,

    Check out the purchasing policies, specifically the policy rule type "Reapproval rule for purchase orders"

  • Verified answer
    Muhammad Fahad Profile Picture
    Muhammad Fahad 470 on at

    Dear Fatih,

    Thanks for your guidance. It resolved my Requirement # 2.

    I read your document through the link u mentioned above. Please make a little change, it might be a typing mistake in your document.

    8. Activate automatic approval action in your workflow's approval elements, set them to approve for the condition "Purchase orders.Requires purchase order re-approval=No"

    It should be set to"Yes" instead of No.

    Thanks.

    Fahad.

  • Muhammad Fahad Profile Picture
    Muhammad Fahad 470 on at

    Dear Andrewbaehr,

    Thanks for your guidance.

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

News and Announcements

Check out the Community Spotlight Video Series

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans