Summary: Vendor Invoice workflow is giving error on Approval or Rejection of Workflow. (Accounts payable/Common/Vendor invoices/Pending vendor invoices) Error Message: SysWorkflowWorkItem-completeNotification Error in call of method EventContextInformation.unpack The review process for vendor invoice has not been submitted for review. Contact the administrator to correct the error and restart the review process Error Message as screenshot: Technical Reason of error/ Call Stack: As we click Approve, system prompts for dialog to enter comments. We put comments and click ok. It goes fine thought all classes but it fails to approve the workflow. Below is full call stack that shows from to where it goes after Clicking Approve button. (S)\Classes\EventNotification\getFromInbox,28, (S)\Classes\SysWorkflowWorkItem\completeNotification,21, (S)\Classes\SysWorkflowWorkItem\completeWorkItem,256, (S)\Classes\SysWorkflowWorkItem\complete,53, (S)\Classes\WorkflowWorkItem\takeAction,47, (C)\Classes\WorkflowWorkItemActionManager\dispatchWorkItemAction,67, (C)\Classes\WorkflowWorkItemActionManager\takeWorkItemAction,8, (C)\Classes\WorkflowWorkItemActionManager\runWorkflowWorkItemAction,22, (C)\Classes\WorkflowWorkItemActionManager\run,16, (C)\Classes\WorkflowWorkItemActionManager\main,7, (C)\Classes\VendInvoiceHeaderWorkflow\main,105, (C)\Classes\FormFunctionButtonControl\Clicked,0, (C)\Classes\FormMenuButtonControl\Clicked,0 Basically it fails at blow line of code of Classes\EventNotification\getFromInbox eci.unpack(inboxData.Data);//here is point of failure Reason is simple that system fails to find record using primary key at below location. Classes\EventNotification\getFromInbox Below is Culprit line of Code, which fails to find a record, though there is data in buffer inbox record = SysDictTable::findFromKeyData(inbox.AlertTableId, inbox.keyFieldData() ); Version of My AX Application Version: 6.3.2000.326 (AX 2012 R3 CU9) Kernel Version: 6.3.2000.326 What Microsoft Says about this? As per Microsoft it’s an issue and they have fixed it at KB 3104794 I applied the recommended KB at infected environment but it hasn’t healed wounds, to fix the issue.
↧