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
Invoice Settlements/Discounts/Reversals
SSRS and SSAS Integration
Workflow
I am trying to create a new automated task in the Purchase Requisition workflow that sets a field on the PurchReqTable. I have one the following:
Created a new class we will call PurchReqSetFieldTask that implements WorkflowElementExecutionEventHandler and has the execute method defined.
Created a new automated task we will call PurchReqSetField.
Set the document property to PurchReqDocument. Set the ExecutionEventHandler property to that of my newly created class PurchReqSetFieldTask
Dragged and dropped the newly created automated task PurchReqSetField to the Workflow type PurchReqReview
Restarted my client
However, I still do not see my new automated class when I go to my procurement workflow edit screen :(
Am I missing a step here that is just not obvious?
Thanks in advance for any help you can offer!
Sincerely,
Anna P.
Hi Anna. I really liked this question. There were some steps that were out of order, such as generating the class before the automated task, but I'm not sure that these would cause an error. When you compiled the application,did you select : "Incremental CIL generation from X++"?
This very well may not be the answer, but I'm just looking for missed steps here. Also, here is the process for completing the automated task step by step:
msdn.microsoft.com/.../gg862506.aspx
I've ran this one several times and never had that error -- though every environment is different, and I could end up having the error tomorrow.
Independent, Freelance Consultant and Dynamics Development Instructor
http://www.instructorbrandon.com
http://www.youtube.com/user/BrandonAhmad
I wanted to say that once I was able to complete the incremental CIL compile and restart my client this all worked as expected :)
I guess that was the missing step! I still forget the CIL compile is so necessary
Awesome Anna. The little things always get me on things like this also. :) I'm glad that it is resolved and hope that it helps more Dynamics Developers when they search for answer to this problem.
Forgot to suggest the incremental compile as an answer. Just doing that here for future searches on the issue.