Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I use Microsoft Dynamic AX 2012
I have a problem on my workflow
I get this error on view history workflow
Stopped (error): X++ Exception: User not found at SysWorkflowHierarchyProvider-resolveSysWorkflowHierarchyProvider-resolveHierarchySysWorkflowQueue-resume
Logical flow that I want to achieve is all workers need approval from their head or supervisor
Here is my Workflow setup
When I see user relation of the account, I think it's the correct
And already assign to work position
And I don't get any problem on supervisor position
Is there any solution or suggestion how to check and solve this issue?Thank in advance
Is this somehow related to your previous thread Workflow Stopped (error): X++ Exception: The hierarchy provider did not return any users?
Did you try to debug the code? If so, what you have found?
Hi Martin Dráb,
I'm sorry if I make duplicate or multiple thread, I thought it's different problem because it shows different error message
I don't know how to debug workflow, but finally I get what's the problem
The problem is same as my thread, but at this time on supervisor user relation
I trace with this query
select DIRPERSONUSER.USER_, HcmPosition.POSITIONID from DIRPERSONUSER inner join DIRPARTYTABLE on DIRPERSONUSER.PERSONPARTY = DIRPARTYTABLE.RECID
inner join HCMWORKER on DIRPERSONUSER.PERSONPARTY = HCMWORKER.Person
inner join HcmPositionWorkerAssignment on HCMWORKER.recid = HcmPositionWorkerAssignment.Worker
inner join HcmPosition on HcmPosition.RECID = HcmPositionWorkerAssignment.POSITION
where DIRPERSONUSER.RECID = [USER RELATION RECORD ID]
[USER RELATION RECORD ID] is from this form
I don't know why, when I choose Person on User Relation it show multiple Person with same name, and it make many user relation problem like my thread before
So what should I do with this thread?
Thank for your respond Martin Dráb
I thought your issue got resolved because you verified the answer in one of your previous posts.
Can you let us know:
1) the person who originates the workflow?
2) the managerial hierarchy and where the workflow originator is included in this hierarchy?
Some screenprints would be good.
Hi Ludwig Reinhard,
The big issue why workflow stopped is because user relation Person does not related to Worker Position
When create user relation, the Person show multiple and that's make a mistake
My solution is signing correct Person with Worker position assigned
Signing workflow originator solve error notification on workflow setup, but didn't affect to the main issue why the workflow stopped
Thank you Ludwig Reinhard
I am not sure if I got the problem.
What does the screenprint show above? Where and how did you open it?
Is this the user form in the system admin module where you have the user Esti... twice?
Would be great if you could help us understanding this issue.
On User Relation form (System administrator > Common > Users > User relation).
As we can see there are 2 named Esti.
When I select with query they have different RecId.
And the correct one is the second Esti who connect with the worker position.
If I go to all worker form, I only see 1 Esti, that's the reason why we confuse to choose when create a user relation.
So I select with sql query to choose the correct one to solve this issue.
I hope it make you clearer about the problem.
You can ask more if you still don't get it.
Business Applications communities