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 :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Purchase order approva...
Microsoft Dynamics AX (Archived)

Purchase order approval assigns the wrong user

(0) ShareShare
ReportReport
Posted on by Tim Schofield

Hi, we have a very simple Hierarchical purchase order approval workflow based on the submitter, and Purchase order approval limits of their 'Reports to position' manager. Everything's working fine in our test system, but we went live this week, and in the Production system every purchase order goes to the user at the top of the hierarchy (the CFO) - it's ignoring the limits of all the lower level managers in the hierarchy. I can't see any real difference in the Signing limits policy setup between Test and Production systems, or the Position hierarchy or the workflow, and I can't even really figure out how to de-bug the problem. Any suggestions anyone?

Thank you.

Tim

*This post is locked for comments

  • Community Member Profile Picture
    Community Member on at

    Hi Tim,

    Given that hierarchies are correct, it looks like an issue of stop condition in the hierarchy selection.

    Could you please attach a screenshot of workflow step for hierarchy selection with stop condition.

    Regards,

    Dwij

  • Tim Schofield Profile Picture
    Tim Schofield on at

    Hi Dwij, The stop condition is that the Employee Purchase Order Approval Limit is greater or equal to the Purchase order Invoice Amount, and as I said it's working in or TEST environment, but after exporting the workflow from Test and importing it into Production it doesn't seem to be finding the Signing limits which are setup in Production.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Hi Tim,

    In that case, could you please check the signing limit parameters - basis should be job and limit restriction checkbox for explicit request should not be checked.

    Could you also check signing policy is defined the organization in question and default signing limits are defined for the Document type (i.e. PO) in question.

    If all above setups are correct - There could possibly be a data migration issue from Test to Prod. I assume workflow import should not have any bugs. I would suggest as a last resort to manually configure workflow and signing limits and verify if it works. Otherwise, without looking into system it's very difficult to help here.

    Regards,

    Dwij

  • Tim Schofield Profile Picture
    Tim Schofield on at

    Thanks for the response – the workflow’s working in the test system which is a copy of PROD, so it looks like all we have to do is restart the workflow and/or the AOS.  Thanks again for the response.

    Tim

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

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