Dynamics 365 CommunityForums Microsoft Dynamics AX (Archived) WorkflowHierarchyProvi...

WorkflowHierarchyProvider implementation has a circular dependency

(0) Share

Report

Posted on by Community Member

Hi,

I am working with managerial hierarchy in workflows and I have used signings limits for approval,but while making a new invoice I am getting following error

Stopped (error): X++ Exception: The WorkflowHierarchyProvider implementation has a circular dependency.
at SysWorkflowHierarchyProvider-resolve
SysWorkflowHierarchyProvider-resolveHierarchy
SysWorkflowQueue-resume

Please help!

Thanks

Pallavi

*This post is locked for comments

All responses (4)

Answers (0)

Community member 2 on at

Like (0)

Report

WorkflowHierarchyProvider implementation has a circular dependency

Was this issue resolved? And if so, how?

thanks in advance

Marcy
Community Member on at

Like (0)

Report

RE: Stopped (error): X++ Exception: The WorkflowHierarchyProvider implementation has a circular dependency. at SysWorkflowHierarchyProvider-resolve SysWorkflowHierarchyProvider-resolveHierarchy SysWorkflowQueue-resume

Hi Lulian,

In my case i am working with vendor invoices in which the creator of invoice can by user and for the approval i am using the particular hierarchy..
Iulian Cordobin 8,201 on at

Like (0)

Report

RE: Stopped (error): X++ Exception: The WorkflowHierarchyProvider implementation has a circular dependency. at SysWorkflowHierarchyProvider-resolve SysWorkflowHierarchyProvider-resolveHierarchy SysWorkflowQueue-resume

Also, I presumed in the previous post that you are using the standard Hierarchy provider and not a custom one, is this the case?
Suggested answer

Iulian Cordobin 8,201 on at

Like (0)

Report

RE: Stopped (error): X++ Exception: The WorkflowHierarchyProvider implementation has a circular dependency. at SysWorkflowHierarchyProvider-resolve SysWorkflowHierarchyProvider-resolveHierarchy SysWorkflowQueue-resume

As the error message is saying, your setup in the management hierarchy (Organization positions) is wrong.

Somewhere in your setup you have assigned a person to be the 'report to position' for a person that already report to it (person A reports to B, B to C, and C to A).

Review the hierarchy and fix this.