Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
I am having an issue with our Purchase Requisition Workflow. In general it is working well, however all of a sudden 1 user is failing with a requisition that is over 100k despite the spending limit being 500K. Another user just stopped working at any amount. Can anyone help with some steps to troubleshoot this issue?
So far I have checked the Hierarchy of workers and positions. Every Worker has a position that reports to another Postition. Interestingly both users that have an issue report to the CEO. Checked the spending limit policy. I have even removed all entries in the policy and reentered them.Confirmed the approving Worker has a relationship to a userId
Any help would be appreciated.
Not that I have the solution for you, but I have similary problem.
I tried to make use of policy rules apllied for jobs.
I created users and recruited them to
Supply chain manager
And I setup approval limits to each position.
But the workflow stops allready when escalating to purchase manager.
Did you get a solution, and was it in this way you created your workflow.
Your help also would be appreciated.
Afterwards I got this working but have another issue.
If the users are buying for a project, the approval limits are higher, say the purchaser may buy in normal situations for 5.000 DKK, but for a project this might be 50.000 DKK.
But only one limit can be put into the position. Is it possible somehow to linked this to the position, as we don't want to make these settings user specific.
I am not sure this can be done. Im sure you could something custom. My knowledge is basically limited by my experience.
thanks for your reply. I will try figuring this out by maybe modifying the 'Hierarchy provider' for the workflow.
i think you don't have to develop here. You can create the workflow configration twice and set a condition on each workflow, if the user is buyer or not so one of the the workflow configs start. In that your can the specify what's to do.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13