D365 FO Execute action - Workflow Workitem complete - Error

[Pratik6]

Hello All,

I am trying to complete D365 Workflow Workitem using Power Automate. I am using D365 Execute action and its failing continuously. Can anyone please help . 

Error - 

An error has occurred. Exception occurred while executing action complete on Entity WorkflowWorkItem: Unable to complete because action is not in a state that can be completed. Exception has been thrown by the target of an invocation.
clientRequestId: 1ad7232a-0b7f-41df-9dca-423a7ceef526

Steps to reproduce the issue - 

1. Create flow with template - Complete Dynamics 365 for Finance and Operations workflow work items (PU29)
2. Assign D365 workflow workitem as trigger 
3. Submit D365 FO workflow used as trigger above
4. It will trigger this flow and try to complete workitem in D365 (which is failing)

I am facing same issue for multiple clients and raised support case with MS support as well but no resolution yet.  

[Abdul810]

Hi Pratik, did you got the solution for this problem? I am facing this too.

[SteveMcGraw]

Same here, this issue started shortly after the 10.0.39 F&O update. We noticed that if the workflow is in stopped status, approvals are successful. The issue appears to be related to the validation function on WorkflowWorkItem. It is driving us crazy. If you find a resolution please let us know.

[SteveMcGraw · Accepted solution]

Ok so our wonderful consultant figured this out for us. Here is what he wrote:

There is a MS standard bug which I found in the class “VendInvoiceWorkflowValidation”.

It is taking the invoice as duplication record and make the flag “isInvoiceNumberfreeForUse” =  false

That is the reason it is throwing error that “Unable to complete because action is not in a state that can be completed.”

Basically the complete action includes a validation, the validation sees its own invoice number, and since the invoice is under review, the validation fails.

He also said that we don't have access to touch this code ourselves and will have to wait on a fix from Microsoft. I am putting in a ticket now.

[Pratik6]

@SteveMcGraw - That's great! I also have ticket open with Microsoft for serveral month. I will let them know these steps. Hope to get it fixed soon. 

[SteveMcGraw]

Here is our microsoft ticket number. I included code screenshots of exactly where the validation fails in the referenced function: 2405010040002963

[JustinOfMerit]

Adding our SR to the very same puppy pile, 2405030010004870... MS support has not had much to say as of yet...

[SteveMcGraw]

Our consultant is going to meet with microsoft tech support and demonstrate the error in the code. Shout out to HSO, they do great work!

[SteveMcGraw]

Bug submitted by MS support

[JustinOfMerit]

I got them to submit a bug as well... There is a kill switch flight for the new code that they can enable to fix the issue, it's on the VendInvoiceCheckDupNumInRunningWorkflowFlight...

[SteveMcGraw]

Thanks Justin, is that the fix or a workaround? I don't know what unintended consequences this would have. Thank you!

[JustinOfMerit]

It's a temporary fix I would say. MS still has to get the validation code working correctly. As it stands it seems that validation "isn't working", hence the "bug" nature of it all. I would say to unblock things, just ask support to use the flight kill switch, but keep an eye out for a Quality Update hotfix to actually correct the code.

[SteveMcGraw]

Justin,

They confirmed the change only affects new validation code, so we had them turn it on and it resolved the issue. Thanks for your help!

[mikkelhansen]

Hi Steve
What was the solution to the issue? I experience the same thing after version .39 - is it something, we can solve or did Microsoft do something in order to resolve the issue 

[JustinOfMerit]

Hey Mikkel, It's a MS fix. There was a bug in some validation logic in versions prior to 41 (Issue #936599). To fix it Support should enable the kill switch flight VendInvoiceCheckDupNumInRunningWorkflowFlight.

Cheers,

JB